Develop Bugs

[JDCTeam][TREBLE][v6 RC2][Gemini] The Full Treble support project

{
"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"
}
The Full Treble Project for MI5 Gemini
Brought to you by Jflte DevConnection Team​
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We're 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 TREBLE
* SUPPORT 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.
*
*/
What is Project Treble:
Project Treble basically partitions your device into two separate partitions, a system and a vendor: system contains your generic system image, while vendor partition has your device specific files required for booting and running your phone. This way we can easily change the system image and be able to run our device on different system images with the same kernel and vendor partition
Read more about Project Treble
Gemini hardware vs Treble implementation:
Gemini is an ARM64 and A-ONLY device. This means that regarding the GSI images (GSI = Generic System Image) to be used, you need to get ARM64 and A-ONLY system images.
Available GSI downloads:
Up today, thanks to @phhusson and other devs, are available a bunch of Android 9.0 system images that can be flashed on Gemini.
You can find these Gsi at the following links:
- ANDROID Q (Gsi)... Is just a preview... but it works on our Mi5!!
- Phh AOSP 9.0 (Gsi).
- Resurrection Remix v7.0 (Gsi).
- LineageOS 16.0 (Gsi).
- HavocOS v2.0 (Gsi) (Use A only).
- ViperOS v6.0 (Gsi) (Use A only).
- JDC AOSP 9.0 (PURE AOSP Gsi, built from sources, just for testing purpose, no gapps support for this preview version).
- GSI & sGSI List page
Treble implementation and download:
JDCTeam is working from latest months of 2017 to implement on Gemini (un-supported from producer) the full support of Treble.
Thanks to @sir mordred, we reached on MI5 the full working status... from v5 we moved to full versioned vndk v28 (aka PIE support... and Q ready!).
NOTE: just to be clear, it's a work in progress development...
We tested with some available Gsi and we put over here some links to these images.
We are sharing a TWRP flashable zip that include vendor and boot images (flash only through TWRP 3.2.3-0 Official).
NOTE: ONLY with TWRP 3.2.3-0 version is possible to handle the treble flash!​
How to use:
Download the TREBLE zip provided here: Mediafire
Download a GSI image (Remember: ARM64 and A-ONLY version)
Reboot to recovery (TWRP 3.3.1-0 REQUIRED)
Clean the device (wipe Dalvik/Cache/System/Data partitions)
Flash Treble gemini zip
Flash the GSI system image you wish to use
Reboot
---> Video on How to install <---
Screenshots:
Youtube review: (To Be Updated when new links available)
- ANDROID Q Gsi on MI5 (How to Install) ---> Click here to play the video
- ANDROID Q Gsi on MI5 ---> Click here to play the video
- RR v7.0.0 Gsi on MI5 ---> Click here to play the video
- PHH AOSP 8.1 Gsi on MI5 ---> Click here to play the video
- AEX 8.1 Gsi on MI5 ---> Click here to play the video
What's working (... and not working):
The development is now @ an RC status (this is not a rom)... you have the possibility to have a look and test the phone with a GSI rom... let us know what does not work (not related to the GSI itself)!!
Issue reporting:
We already say that this is not the place to report issues or bugs ROM related... but in any case a bug encountered can be linked to the treble support not perfect or missing supported features... be free to post about issues you encountered, and please provide logs with the description of the issue. We will check the logs to understand the reason, and in case of fixes to be done, we will update on post#3 (MISCELLANEA) a kind of todo list for us and for users as a "bug list"... but the meaning is "what has to be checked/fixed to get a better treble support for future".
Any question?
If you have any question about, please check first on the post#2 (FAQ) to see if your question has already an answer... if not, post in the thread and we will give you informations.
Sources
GitHub
Social
YouTube: JDCTeam TV
XDA News: Read article
Credits
JDCTeam
LinageOS
Google
MI5Devs
Special thanks:
@sir mordred (developer)
@musabcel (for his test support)
Team Codefire - JDCTeam-Build03
XDA:DevDB Information
GEMINI Full Treble support project, ROM for the Xiaomi Mi 5
Contributors
smeroni68, sir mordred, mzo, ktulu84
Source Code: https://github.com/Project-Treble-Mi5
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Latest available
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: v6
Stable Release Date: 2019-03-16
Created 2018-03-10
Last Updated 2019-06-27

FAQ Section...
This is the FAQ (Frequently Asked Questions).
Have a look here before asking in the thread... in the worst case you will not find the answer you are searching!
If this section is useful for most users needs, I'll be glad to continue investing time to update this Q/A list!!​​
Q1:Fingerprint wake/home button works?
A: Yes, now we have the complete support and this feature is available on standard GSI roms (treble support is ready for it)
Q2: How can I revert back from treble to custom ROM whenever required?
A: Just flash the custom rom you like from TWRP and that's all. Custom rom flash will overwrite the boot.img,system and vendor partitions.
Q3: If I revert to a Custom rom, what I need to do to restore treble support?
A: Just flash the Treble zip through TWRP as the first time. Treble support need boot.img and vendor.img to be installed into the phone... nothing more... nothing less...
Q4: Phh GSI rom is quite poor in functionality. Why?
A: The purpose of Phh GSI AOSP rom is not to be a custom/featured rom. It is an experimental project that is born to have a common rom (better to say the same system.img) usable on many devices with treble support.
This support can be native, acquired after an Oreo original update or as we have done a custom integration on an "unsupported" device.
The meaning today of using a GSI rom is not to be a perfect rom for dayly use... or let's say, it can be a dayly rom only for users that like pure vanilla code.
In future we hope that many others custom roms will move to be a GSI (as JDC will try to do), so we will have the treble base to use these new project also on our devices.
Q5: If a new version of treble support is out, did I need to flash it or not?
A: Our project is on the way. This means that if is available a new update from us, it is for sure an enhancement with more support of feature or fixes.
In case you will need to install a GSI rom, check always here if there is any new version and get it.
In case you are running a custom rom without treble support, DO NOT update with treble flash, because most probably you will break your current installation.
Treble flash is 100% safe from the phone point of view... isn't safe for your current installation!! Why? Mainly because your current boot.img will be overwritten with treble support... 99% you will get a bootloop with a not treble rom!
Q6: How to get ROOT on phh gsi?
A: Firstly download the phh-gapps-su image. After installation, go to the market and install "phh superuser" app to manage the su access for the apps that need it. In the other cases, you can flash from TWRP the correct Magisk zip to gain root.
Q7: Where I can find the GSI images available?
A: Have a look in the OP post over here... there you can find the available ones. In any case here the LINK to the Treble Enabled Device Development section on XDA or here on GSI & sGSI List page
Q8: Everytime I entered the password, it says Decryption Unsuccessful!
A: You have internal SD encrypted. If after MIUI stock, you haven't FORMATTED the internal SD (FORMAT is not WIPE... Format will erase all data and files from the phone, so you must know what you are doing before formatting), the phone result as encrypted, so the rom is asking the password to decrypt the datas... Decryption Unsuccesful clearly states that the decryption procedure is not working. Post about the issue on the GSI rom you are using and provide logs to the developer to help digging the problem... if Developer will answer that encryption is not supported, you can only do one thing: backup all your data, files and pictures on an external storage (eg. a PC) and procede with a FORMAT DATA from TWRP to "destroy" the encryption and "free your phone from it"!
Q9: Is Google Camera working on Gsi?
A: Yes. But remember you need to install gapps package to let gcam works as it should.
We tested Gcam up to v6.1.021 on AOSiP Gsi. If you have greenish selfies pics, go in the Settings -> Fix ->and enable the fix for Front Camera and reboot. For SlowMotion, set 120fps.
Q10: Why can't flash a micro gapps and only pico is flashable?
A: If you get an error of Insufficent space on system partition, you need to resize the partition. Do in this way:
Flash the SYSTEM.IMG you wanna use (select a Vanilla based one)
Reboot to RECOVERY
MOUNT the SYSTEM partition
Go in WIPE menu -> ADVANCED WIPE -> select SYSTEM from the list and press the button REPAIR OR CHANGE FILE SYSTEM
select RESIZE FILE SYSTEM
than SWIPE to execute the command...
in case of error (you will see in red), repeat the RESIZE until it goes completed (Resizing... Done)
After this operation, the system partition will be resized to his maximum dimension (on Mi5 is around 2992MB)
before the installation of gapps package, do a REBOOT to recovery and after MOUNT the SYSTEM partition (check that it is really mounted)
Now you can flash the micro gapps without problem.
Q11: Is there any Magisk version working on Treble gsi?
A: Yes, you need to get v18.1 version or newer with treble support (check around).
Q12: VoLTE is working[/B]?
A: Yes. Install this ims.apk to use it!
Q13: ADB Logs are needed in case of Issue reporting...
A: In case you need help and want report an issue (eg. a boot problem), we need logcat of the phone. Just as sample, we report here what to do (but you must able to do by yourself... we are not giving help on how to do...)
prepare a PC (with adb package to support debug via usb connection)
flash on the phone our treble and the GSI image (just these 2 files, not any patch or other stuff)
reboot the phone
connect the usb cable
after the Mi logo screen, wait to hear from PC a sound that means the usb periferial has been recognised
go in a command window and type:
--> adb devices (if the phone is connected, you will see the code written after the command executed)
--> adb shell logcat > bootlog.txt (this will start real time recording of logs into the pc in the bootlog.txt file)
--> when the phone has completed boot/reboot (eg. a boot loop or fastboot), you need to press Ctrl+C from keyboard to stop log recording.
send attached to the issue description post the bootlog.txt
...let's dev check what's happening by reading the logcat.
... list will be updated...

Miscellanea...
Download (public versions history)
Here you can find the shared folder with all the version released of Treble support: GEMINI-TREBLE
Changelog's
v6 (20190316) - Release Candidate 2 full versioned_vndk v28
- VERSİONED_VNDK support is fully implemented
- FIXED NFC support
- FIXED Ambient Display main icon size and settings menu icons style... Thanks to Subezhj for helping fixing.
- FIXED ConfigPanel - Fingerprint settings menu icons style
v5 (20190308) - Release Candidate full versioned_vndk v28
- VERSİONED_VNDK support is fully implemented
- Mostly all library dependencies between system/vendor which are called as violations against treble's rule are succesfully eliminated
- Updated kernel as per treble's kernel docs (enforced)
- Vendor image's version is now 28
- Misc updates and fixes
- GSI Pie roms support (check in OP for some links)
- JDC PIE GSI rom given just as a preview for testing (JDC PIE GSI is build from sources without ANY hack!!)... It's pure AOSP as Google bring to their devices... NOTE: No support for gapps... they do not complete setup... you are advised.
v4 (20180409) - Beta partially versioned_vndk with the following updates:
- VERSİONED_VNDK support is partially implemented
- Lots of library dependencies between system/vendor which are called as violations against treble's rule are succesfully eliminated, only small number of lib dependencies which needs to be resolved are left
- Updated kernel as per treble's kernel docs
- Vendor image is now using google's stock vndk-sp, ll-ndk libs which are called as treble layer libs
- Vendor image's version is now 27.1.0
- Misc updates and fixes
v3 (20180329) - Beta status with the following updates:
- Updated camera Hal from latest qualcomm 8996 repo
- Hexedited more libs and removed more vendor system dependency (better treble and preparation for versioned vndk)
- Updated wifi configs from lates CAF
v2 (20180318) - Still alpha build with the following updates:
- Upstreamed kernel
- Hexedited blobs to correct path (for treble)
- Linker issues fixed
- Vendor overlays
- Latest device tree updates from CAF and miui oreo beta
- Disabled non-working apps (custom xiaomi doze package and configpanel app which were designed to work with LOS APIs)
- Disabled userspace thermal hal initialization which we dont have in cameraHal (faster cam launch)
- Increased jpeg quality parameters
- other misc. dev tree updates
v1 (20180310) - Initial release (Alpha)
Reported/Known Issues
- Camera works perfectly, but on some apk after a shot is taken with Flash active, the camera do not get more pictures... Close the app will clear the issue and you can get other pictures! Suggestion: do not use the flash with this camera apk if you have the issue! ... or use a working camera apk (is a better solution)!
to be updated...

Big thanx and credits also goes to @smeroni68
All of the story is started with the identifying unused CUST partition which xiaomi left on our device Mi5 https://forum.xda-developers.com/showpost.php?p=74702470&postcount=300
And after we determined that the /cust partiton is unused on AOSP roms, we used it as /vendor partition as per the requirement of Full-Treble https://github.com/sirmordred/android_device_xiaomi_gemini-twrp/commit/5faf9c4e162e8144b71f87d6d21c384931b1ac0c nearly 3 month ago
And that is also the reason of nearly all devices which get Full-Treble support via custom implementation, are Xiaomi devices (Redmi Note 4, Mi5S and our Mi5)
Thanx also to my teammates who contributed this project :good:
Our goal is now separating/isolating all vendor <=> system interactions (which will be enforced on future android releases for treble devices) and stabilizing vendor.img while getting closer to pure AOSP sources
Enjoy

...

...

Finally we are out for both MI5 and MI5S... yeah... now let's go ahead...

Thanks for all JDCTeam

Great Job dude! Finally we got treble. Downloading now. Can't wait flashing.
通过我的 MI 5 上的 Tapatalk发言

Thank you Sir, downloading now

Great news ..only one query .. How can I revert back from treble to custom ROM whenever required?

kishan314 said:
Great news ..only one query .. How can I revert back from treble to custom ROM whenever required?
Click to expand...
Click to collapse
Good question... I'll report also in post#2 in FAQ section.
Q: How can I revert back from treble to custom ROM whenever required?
A: Just flash the custom rom you like from TWRP and that's all. Custom rom flash will overwrite the boot.img and the system partition... vendor partition will stay there waiting for your next test!

So... P GSI is coming for the "old" Mi5. Thank u guys! This is the way

atembleque said:
So... P GSI is coming for the "old" Mi5. Thank u guys! This is the way
Click to expand...
Click to collapse
This is something we can try to build... but only when sources of P will be released and will be good to build an AOSP based on them...

Very very thankful

Thanks for your hardwork, downloading now.

When charging, the battery icon won't show. The bug is phh's?
Sent from my MI 5 using Tapatalk

Installed. Yeap, we finally got a vanilla android
For first alpha, it working flawlessly.
Some bugs i founded.
1. After magisk install on stock kernel, got bootloop. Fixed after installing AEXMod latest kernel.
2. Gcam not working. buildprop (vendor folder) doesnt help. Got FC anyway
3. HMP... stock governor settings cant provide smooth scrolling in settings, 820 sd stuttering like 210, okay. It happens on every gemini hmp kernel on 8.1 oreo. Maybe some to perfd related. Need EAS.
4. Gpay wont work, magisk can't help, maybe device id change will help
All other working fine

MichaelPan01 said:
When charging, the battery icon won't show. The bug is phh's?
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
Here it is working.
Have you set the battery icon visibility status under the statusbar settings?
StealthHD said:
Installed. Yeap, we finally got a vanilla android
For first alpha, it working flawlessly.
Some bugs i founded.
1. After magisk install on stock kernel, got bootloop. Fixed after installing AEXMod latest kernel.
2. Gcam not working. buildprop (vendor folder) doesnt help. Got FC anyway
3. HMP... stock governor settings cant provide smooth scrolling in settings, 820 sd stuttering like 210, okay. It happens on every gemini hmp kernel on 8.1 oreo. Maybe some to perfd related. Need EAS.
4. Gpay wont work, magisk can't help, maybe device id change will help
All other working fine
Click to expand...
Click to collapse
1) Phh rom support natively Phh superuser app (from market) with stock kernel and phh-gapps-su gsi image.
2) Gcam require API2/HAL3 support, and on phh gsi hasn't been implemented (as written is an experimental rom with the meaning to be compatible with stock Oreo treble devices). Instead, it has API1/HAL1 support for stock vanilla camera.
3) Stock kernel is HMP. We do not develop till now the EAS kernel on stock treble kernel (we will do for our JDC gsi).
4) Magisk is clearly reported into Phh thread to not be used. In custom development we have a plus, because we can change the kernel (as you have done)...
Thanks for this testing report.

[ROM][OFFICIAL][gts4lvwifi][10] LineageOS 17.1

{
"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"
}
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. You can also view the Changelog for a full list of changes & features.
Instructions :
Download the latest build and gapps
Reboot to recovery
Flash the latest build and gapps
Reboot
Downloads :
Builds : https://download.lineageos.org/gts4lvwifi
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
[ROM][OFFICIAL][gts4lvwifi][10] LineageOS 17.1, ROM for the Samsung Galaxy Tab S5e
Contributors
LuK1337
Source Code: https://github.com/LineageOS
ROM OS Version: Windows 8 Mobile
Version Information
Status: Testing
Created 2019-09-24
Last Updated 2020-04-01

-- bit more friendly stock -> lineage instructions --
1. Unlock the bootloader
- Connect to WiFi network
- Enable OEM Unlock in developer options
- Turn off the tablet
- Boot to download mode manually by plugging in USB and holding all the buttons for few seconds
- Follow instructions on the screen
2. Connect to WiFi network and make sure OEM Unlock in developer options is still checked
3. Flash custom VBMeta image ( https://dl.twrp.me/gts4lvwifi/vbmeta.tar.html ) in Odin ( use AP slot )
4. After flashing VBMeta, boot to stock. It'll likely ask you to wipe data, if so do that
5. Connect to WiFi network and make sure OEM Unlock in developer options is still checked
6. Now you can flash TWRP ( https://dl.twrp.me/gts4lvwifi ) in Odin ( use AP slot once again ), for convenience you can hold volume up while flashing it so that you boot to recovery right after it's flashed
7. Install Lineage × whatever else you need ( gapps, addon-su, ... )
8. Format data
9. Reboot ( make sure to not install TWRP app when TWRP asks you to )
---
Also Odin download for those who can't find it on their own https://build.nethunter.com/samsung-tools/Odin_3.13.1.zip
( sha1sum 1057496afa34bfdf7e77caf0b99207dca77fcb2d )

Builds 20200824+ depend on Android 10 firmware, and thus from now on the recovery will abort the installation if you're still on Android 9 one.
You can update the firmware by flashing following Odin package: https://github.com/luk1337/gts4lv-fw/releases/tag/T720XXS2CUA3.
After the firmware update you should be able to flash newer builds.

Well.. that was faster than expected. Thank you very much for your dedication.
Which gapps are you currently using or recommending? Opengapps doesn't seem to have gapps for 10 yet.
Also any special instructions for flashing when coming from your previous los16 rom?

LuK1337 said:
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. You can also view the Changelog for a full list of changes & features.
Instructions :
Download the latest build and gapps
Reboot to recovery
Flash the latest build and gapps
Reboot
Downloads :
Builds :
https://www.androidfilehost.com/?w=files&flid=299579
http://downloads.codefi.re/jdcteam/luk/lineage-17_0/gts4lvwifi
https://sourceforge.net/projects/luk-lineageos/files/gts4lvwifi/lineage-17.0
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
[ROM][UNOFFICIAL][gts4lvwifi][10] LineageOS 17.0, ROM for the Samsung Galaxy Tab S5e
Contributors
LuK1337
Source Code: https://github.com/LineageOS
ROM OS Version: Windows 8 Mobile
Version Information
Status: Testing
Created 2019-09-24
Last Updated 2019-09-24
Click to expand...
Click to collapse
Wow!!!! Thanks op!

andre0005 said:
Well.. that was faster than expected. Thank you very much for your dedication.
Which gapps are you currently using or recommending? Opengapps doesn't seem to have gapps for 10 yet.
Also any special instructions for flashing when coming from your previous los16 rom?
Click to expand...
Click to collapse
Apparently https://sourceforge.net/projects/opengapps/files/arm64/beta/ works.

I had the opportunity to test the image yesterday as kind of a preview. After killing the setup wizzard, it worked really great. The switch from LOS 16 to 17 was easy.
Rooting had to be done with magisk (current stable was fine) as Luk told me that superSU probably won't work.
I eventually reverted to LOS 16 mainly because of personal discomfort. No Trebuchet, some settings dialogues not (yet) ported and Titanium Backup did not work (there were no buttons displayed - could not even press the problems? button as it was not there ). I personally decided to wait a bit until I will return to LOS 17 on that device.

That was fast. You got me

inka$$o said:
I had the opportunity to test the image yesterday as kind of a preview. After killing the setup wizzard, it worked really great. The switch from LOS 16 to 17 was easy.
Rooting had to be done with magisk (current stable was fine) as Luk told me that superSU probably won't work.
I eventually reverted to LOS 16 mainly because of personal discomfort. No Trebuchet, some settings dialogues not (yet) ported and Titanium Backup did not work (there were no buttons displayed - could not even press the problems? button as it was not there ). I personally decided to wait a bit until I will return to LOS 17 on that device.
Click to expand...
Click to collapse
Did you perform a full wipe before flashing?
Also how did you 'kill' the setup wizard?

There is an issue with twrp decrypting storage on Los 17. Is this more than likely a twrp issue?
I also can't install apps, probably because no access to SD card.

suzook said:
There is an issue with twrp decrypting storage on Los 17. Is this more than likely a twrp issue?
Click to expand...
Click to collapse
TWRP issue.

LuK1337 said:
TWRP issue.
Click to expand...
Click to collapse
Apps won't install from play store also
Unfortunately I can't download anything, since SD card is encrypted. Guess I will go back to Los 16. Thanks anyway op.

suzook said:
Apps won't install from play store also
Unfortunately I can't download anything, since SD card is encrypted. Guess I will go back to Los 16. Thanks anyway op.
Click to expand...
Click to collapse
>Apps won't install from play store also
Format data; reboot and they should install fine now.

LuK1337 said:
>Apps won't install from play store also
Format data; reboot and they should install fine now.
Click to expand...
Click to collapse
Will give it a shot.

andre0005 said:
Did you perform a full wipe before flashing?
Also how did you 'kill' the setup wizard?
Click to expand...
Click to collapse
I started with my device running LOS16 already. If you're coming from stock, you should stick to the instructions for the LOS16 installation in the other thread - just use instead of LOS16 image the LOS17 image.
If you have already LOS16 on the device:
-> Boot to Recovery
-> install LOS 17 image
-> if desired stable Magisk for rooting
-> if desired these openGAPPS (was told to use them - they worked fine)
-> FORMAT data (wipe doesn't do the trick, as it doesn't do it when installing LOS 16)
After facing the problem with the setup wizzard I was told to simply delete it.
Boot to Recovery, mount system partition and open the terminal.
The command is:
rm -rf /system/priv-app/SetupWizard
After that, the wizard is gone and you can boot to system. You'll have to manually go through the settings to set up everything though.

Are there any launchers other than the included that work with the new gesture navigation?

andre0005 said:
Are there any launchers other than the included that work with the new gesture navigation?
Click to expand...
Click to collapse
No.

OK, got it set up properly with the format data. Just a couple things. Black theme doesn't work, and immersive mode force crashes settings app when trying to access it. Not complaining, just letting you know.

suzook said:
OK, got it set up properly with the format data. Just a couple things. Black theme doesn't work, and immersive mode force crashes settings app when trying to access it. Not complaining, just letting you know.
Click to expand...
Click to collapse
Use a standalone dark theme toggle, not 'Style' one.

@LuK1337 Thanks a lot for the build. Time to buy the Tablet.
One Question:
 @LuK1337 or anyone, are the corners rounded like that of the stock ROM or are the corners sharp?

[ROM][13][UNOFFICIAL] LineageOS 20 - microG [OnePlus Nord/avicii]

{
"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"
}
​
You care a lot about privacy and security? You want an up to date LineageOS build that will not hold you back in regards of user experience?
Then LineageOS 20 microG edition is right for you! (Non-microG vanilla LineageOS version also available).​
Click to expand...
Click to collapse
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, 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.
What's working :
Boots
RIL
Fingerprint
Wi-Fi
Bluetooth
Camera
Audio
Sensors
Flash
GPS
Alert Slider
NFC
DT2W
Known issues :
-
Versions :
There are 2 versions available:
-LineageOS 20 with microG (includes microG, FDroid and AuroraStore)
-LineageOS 20 vanilla (no Gapps / nothing added)
In order to prevent problems please use the recovery image included in this release!
Instructions :
-Download the ROM and recovery image
-Boot into bootloader: adb reboot bootloader
-Boot the recovery image: fastboot boot recovery.img
-Format data / do a factory reset in recovery
-Go to Apply update and choose Apply from ADB
-Sideload the rom: adb sideload rom.zip
Please note:
in order to enable push notifications open up microG services core,
set up your Google account and enable device registration & cloud messaging.
Downloads :
-Recovery image: *Link*
-LineageOS 20 with microG included: *Link*
-LineageOS 20 vanilla (no Gapps included): *Link*
Android OS version: 13
Build author/ROM Maintainer: @MajorP93, @KakatkarAkshay
Kernel Source: *Link*
Device Tree: *Link*
Based on: LineageOS
Status: Stable
Current Stable Version: 20
Stable Release Date: Updated monthly
Created: 2023-01-22
Last Updated: 2023-02-20
Telegram Group: *Link*
Special Thanks:
- to the LineageOS and microG team
- @KakatkarAkshay for putting in awesome work towards bringing up OOS12 firmware based trees.​

HOW TO GET GAPPS IN THE VANILLA VERSION OF THIS ROM:
Reference: *Link*
Follow these steps:
-Download Gapps from here: *Link* (MindTheGapps-13.0.0-arm64)
-Boot into bootloader: adb reboot bootloader
-Boot the recovery image: fastboot boot recovery.img
-Format data / do a factory reset in recovery
-Go to Apply update and choose Apply from ADB
-Sideload the vanilla version of the rom: adb sideload rom.zip
-Reboot into recovery: click advanced --> reboot to recovery (!important do not start LineageOS yet)
-Go to Apply update again and choose Apply from ADB
-Sideload the Gapps package you just downloaded: adb sideload gapps.zip, when prompted select "install anyway" after the "signature verification" message.
UPDATING THE ROM:
Unless I say the opposite in the update announcement, this ROM can be updated using the dirty flash method.
In order to do so, follow these steps:
-Download the new version of the ROM you are using (microG/vanilla)
-Reboot into recovery: adb reboot recovery
-DO NOT CLICK ON FACTORY RESET / WIPE DATA
-Flash the Zip-File of the new ROM: adb sideload rom.zip
Important: if you are using the vanilla version of the ROM,
you have to re-flash Gapps after updating and before starting LineageOS:
-Reboot into recovery: click advanced --> reboot to recovery
-Go to Apply update again and choose Apply from ADB
-Download Gapps from the link above
-Sideload the Gapps package you just downloaded: adb sideload gapps.zip, when prompted select "install anyway" after the "signature verification" message.​

I was waiting for this clean Lineage port, but i need to make sure that everything works before i give it a go. I only have a single phone and i need pretty much eveything to work (NFC, Camera with decent quality, banking apps and AOD).
I will keep my eye on this thread. Thank you.

Thank you so much.
If I install your microG version now, will I be able to dirty flash the version from https://lineage.microg.org/ when it becomes official?

sorin000 said:
I was waiting for this clean Lineage port, but i need to make sure that everything works before i give it a go. I only have a single phone and i need pretty much eveything to work (NFC, Camera with decent quality, banking apps and AOD).
I will keep my eye on this thread. Thank you.
Click to expand...
Click to collapse
I am using this build as a daily driver myself and so far everything works well.
As for camera quality: the stock LineageOS camera app is not really good but in the microG version of this build you can install GCam without any issues.

uhuhuh said:
Thank you so much.
If I install your microG version now, will I be able to dirty flash the version from https://lineage.microg.org/ when it becomes official?
Click to expand...
Click to collapse
In that case formating data (full wipe) would be required. LineageOS has a preinstalled backup tool which makes it easier for you to import your data after a full wipe.
On a side note: it can take a while for this becoming official since LineageOS only accept source-built-kernels. This build here uses the stock prebuilt kernel from OnePlus because OnePlus released buggy kernel sources (NFC broken).
IMO working NFC is important which is why I will start working on making this official once the NFC functionality get's fixed in OnePlus kernel sources.

MajorP93 said:
View attachment 5402769
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
What's working :
Boots
RIL
Fingerprint
Wi-Fi
Bluetooth
Camera
Audio
Sensors
Flash
GPS
Alert Slider
NFC
Known issues :
DT2W
Versions :
There are 2 versions available:
LineageOS 18.1 with microG (includes microG, FDroid and AuroraStore)
LineageOS 18.1 vanilla (no GApps / nothing added)
In order to prevent problems please use the recovery image included in this release!
Instructions :
-Download the ROM and recovery image
-Boot into bootloader: adb reboot bootloader
-Flash the recovery image: fastboot flash recovery recovery.img
-Format data / do a factory reset in recovery
-Reboot into recovery: fastboot reboot recovery
-Go to Apply update and choose Apply from ADB
-Sideload the rom: adb sideload rom.zip
Please note:
in order to enable push notifications open up microG services core,
set up your Google account and enable device registration & cloud messaging.
Downloads :
-Recovery image: *Link*
-LineageOS 18.1 with microG included (recommended): *Link*
-LineageOS 18.1 without additions: *Link*
Android OS version: 11
Build author/ROM Maintainer: @MajorP93
Kernel Source: Stock Prebuilt Kernel
Based on: LineageOS
Status: Stable
Current Stable Version: 18.1
Stable Release Date: Updated monthly
Created: 2021-09-05
Last Updated: 2021-09-05
Special Thanks:
- to the LineageOS and microG team
- @KakatkarAkshay for maintaning PixelExperience avicii device tree on which this build is heavily based on.
- @zephiK for introducing me to the Android development world.​
Click to expand...
Click to collapse
It's great to see a new ROM for the device , especially one that focuses on privacy . Thanks OP , for this awesome new addition to the Nord community , I'll definitely try it out soon !

hi! im found an issue when i flash gapps.. on screen, appear error 70. idk why recovery shows this..

CrazyLyte said:
hi! im found an issue when i flash gapps.. on screen, appear error 70. idk why recovery shows this..
Click to expand...
Click to collapse
Hi!
Did you use OpenGApps Pico and followed the instructions in exact order?
It is important to reboot to recovery after installing LineageOS vanilla und then flash GApps.

MajorP93 said:
Hi!
Did you use OpenGApps Pico and followed the instructions in exact order?
It is important to reboot to recovery after installing LineageOS vanilla und then flash GApps.
Click to expand...
Click to collapse
yes.. it says storage space is insufficient

CrazyLyte said:
yes.. it says storage space is insufficient
Click to expand...
Click to collapse
Thanks for reporting back!
I took the instructions from the official LineageOS wiki and did not test GApps extensively since I only use microG.
I will test this and create an update this week where GApps will work.
In the meantime you can use microG if you want.
It also gives you the ability to use Google stuff.
//EDIT: you can also try BitGApps, those are like OpenGApps Pico but smaller.
I updated the GApps instructions accordingly.
If you want to try those please start over again with the instructions.

MajorP93 said:
Thanks for reporting back!
I took the instructions from the official LineageOS wiki and did not test GApps extensively since I only use microG.
I will test this and create an update this week where GApps will work.
In the meantime you can use microG if you want.
It also gives you the ability to use Google stuff.
Click to expand...
Click to collapse
ty a lot! i wait for next release! anyway, good job.. it is very smooth and fod is pretty fast! im looking forward

long awaited 18.1 is here . downloading right away. as you mentioned Dt2w is not working ..can we try stormbreaker kernel on this rom to enable it?
Also can ROM be flashed with OrFox recovery

MajorP93 said:
Thanks for reporting back!
I took the instructions from the official LineageOS wiki and did not test GApps extensively since I only use microG.
I will test this and create an update this week where GApps will work.
In the meantime you can use microG if you want.
It also gives you the ability to use Google stuff.
//EDIT: you can also try BitGApps, those are like OpenGApps Pico but smaller.
I updated the GApps instructions accordingly.
If you want to try those please start over again with the instructions.
Click to expand...
Click to collapse
same problem. ive tried also with nikgapps core (more smaller).. is a problem for the rom

5fusion said:
long awaited 18.1 is here . downloading right away. as you mentioned Dt2w is not working ..can we try stormbreaker kernel on this rom to enable it?
Click to expand...
Click to collapse
Hey!
I can not ensure that all parts of the ROM will work using Stormbreaker kernel but you can sure try!
CrazyLyte said:
same problem. ive tried also with nikgapps core (more smaller).. is a problem for the rom
Click to expand...
Click to collapse
Thanks for reporting back, I am working on a new release right now in which flashing of GApps will be fixed.

Great job, I found a little bug, when I try to use an app with fingerprint acces the finger print doesn't work

MajorP93 said:
Thanks for reporting back, I am working on a new release right now in which flashing of GApps will be fixed.
Click to expand...
Click to collapse
thanks for your job! when u push new, i flash it immediately

UPDATE 2021-09-07
Changelog:
-LineageOS 18.1 vanilla version: support for flashing GApps has been added (tested and verified with OpenGApps Pico) --> please refer to the instructions above (flashing GApps)
--> Download link in original post has been updated

MajorP93 said:
UPDATE 2021-09-07
Changelog:
-LineageOS 18.1 vanilla version: support for flashing GApps has been added (tested and verified with OpenGApps Pico) --> please refer to the instructions above (flashing GApps)
--> Download link in original post has been updated
Click to expand...
Click to collapse
ty a lot! i have a question.. u use tg? my idea is to create a group for los 18.1 and talk about it (also test the test buids and other as bugs)
so, we can help u to mantain the project up with no bugs pretty important.. let me know, if u want do this. thx in advance

CrazyLyte said:
ty a lot! i have a question.. u use tg? my idea is to create a group for los 18.1 and talk about it (also test the test buids and other as bugs)
so, we can help u to mantain the project up with no bugs pretty important.. let me know, if u want do this. thx in advance
Click to expand...
Click to collapse
Thanks for the suggestion!
I like the idea!
I think this can help with testing while working on making this an official port one day and also help with making this project bigger.
I will see what I can do in this regard when I have the time (set up the group etc.)
Best regards

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

{
"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"
}
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 restores 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 our Gerrit Code Review.
Code:
#include
/*
* 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.
*/
SUPPORTED DEVICES
- ZS620KL (Asus Zenfone 5z)
- ZS621KL (Asus Zenfone 5z)
HOW TO INSTALL LINEAGEOS WITH LINEAGE RECOVERY
Please follow the official LineageOS Wiki instructions for our device
Install LineageOS on Z01R | LineageOS Wiki
wiki.lineageos.org
HOW TO UPDATE LINEAGEOS WITH LINEAGE RECOVERY
Please follow the official LineageOS Wiki instructions for our device
Update LineageOS on Z01R | LineageOS Wiki
wiki.lineageos.org
HOW TO INSTALL LINEAGEOS WITH TWRP
- Unlock the bootloader and install TWRP.
- Download LineageOS. (see Downloads)
- Boot into TWRP.
- Copy the downloaded zip files to the internal SD card.
- Perform a backup of your current ROM. (Optional)
- NOTE! If you're coming from stock ROM? You MUST format data. Wipe > "Format Data" button > type "yes" > keyboard checkbox
- RECOMMENDED: Do a factory reset (clean wipe)! No support if you didn't! (Wipe System, Cache and Data)
- Flash LineageOS zip.
- Flash TWRP installer zip.
- Reboot to TWRP.
- Optional: Install the Google Apps add-on package. (see Downloads)
- Reboot to system.
HOW TO UPDATE LINEAGEOS WITH TWRP
- Download the LineageOS zip(s). (see Downloads)
- Copy the LineageOS zip to the internal SD card.
- Reboot to TWRP.
- Flash LineageOS. (Wiping Cache is optional, but recommended)
- Reboot to TWRP.
- Optional: Install the Google Apps add-on package. (see Downloads)
- Reboot to system.
MAIN DOWNLOADS
Lineage:
- Official:
LineageOS Downloads
download.lineageos.org
- Unofficial:
Package lineage-19.1 - lineageos-for-z01r - OSDN
Package lineage-19.1 - lineageos-for-z01r #osdn
osdn.net
TWRP for Z01R: Official:
ASUS ZenFone 5z 2018
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
GOOGLE APPS (GAPPS) DOWNLOADS
Google apps | LineageOS Wiki
wiki.lineageos.org
GOOGLE CAMERA (GCAM) DOWNLOADS
Google Camera:
Wichaya GCam APKs - Google Camera Port
Modified Google Camera app by Wichaya.
www.celsoazevedo.com
5z's configuration can be found in his configs:
Config Files for Wichaya's 7.3 (v2.8+)
Stable settings for Wichaya's 7.3 (v2.8+) with xml config files support.
www.celsoazevedo.com
DEVELOPER RESOURCES
Asus ZenFone 5Z
Asus ZenFone 5Z has 7 repositories available. Follow their code on GitHub.
github.com
GitHub - LineageOS/android_kernel_asus_sdm845
Contribute to LineageOS/android_kernel_asus_sdm845 development by creating an account on GitHub.
github.com
HOW TO CONTRIBUTE?
Send your patches up for review: https://review.lineageos.org/
Read the guides on the LineageOS Wiki: https://wiki.lineageos.org/
Source Code: https://github.com/LineageOS

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

[ROM][13]LineageOS 20 [with microG] for OnePlus 5 & 5T

{
"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"
}
With the rise of Big Tech and the encroachment of government on our lives, I felt more of a desire to move away from Google and the like. OnePlus 5/5T was built with microG and LineageOS source and is fully functional.
What it is. It's LineageOS with all of Google's closed-source binaries removed and replaced with microG. I.e. no Play services or GAPPS. UnifiedNLP is used as the networking location provider instead of Google's NLP. Aurora Store and F-Droid is installed by default and provides an alternative app store. However, with the Aurora Store, you cannot install all Google Play Store apps such as buy apps.
Other information Google Play Store Alternative If you want to have full access to normal Android Play Store apps, After opening Aurora Store, select the appropriate option. usually option number 1 is the most commonly used with this ROM, unless changed by the user. After setup, you will have access to all apps as usual. Some apps require Play Services and cannot be used.
After installation - Open the microG app --> self-check sections should be successful. Location Services - By default, LocalGsmNlpBackend, which uses the NominatimGeocoderBackend, and NominatimNlpBackend, which uses Mapquest's Noninatim service, are disabled. Open the microG app --> location modules and enable the modules you want. Then restart the device.
It is strongly recommended not to install GApps as this ROM contains a replacement for them.
What everything works
all standard functions
What does not work
You tell me!
Important :Make a full backup of the system via twrp so that you can get back to your old version.
Clean flash
Installation Clean Via twrp
- Back up your data (recommended)
- Remove custom encryption pins/passwords (recommended)
- Boot into twrp go to Delete /Advanced - Wipe system / data / cache / vendor (do not format data - this will erase the internal memory) .
- back to the main menu go to install and find the location where you saved the rom.
- select the rom and then confirm reboot
Dirty flash (Update)
Dirty Flash (OTA) update can be downloaded from lineageos updates and installed on your device.
If it is not possible to install the update automatically, or if you want to install it manually, do the following,
select install in twrp/ parent folder/data/lineageos_updates select the rom install it and restart everything else you want to install.
how to boot into twrp from the system:
settings>system>keys> down to menu point on/off menu
then activate Advanced reboot.
now press the power button right , select reboot a second menu appears,
there you can select Recovery from and it will automatically boot into twrp.
Other information
Note that many features of LineageOS are not yet finished, this is not a device bug and please do not report them,
also do not file bug reports for known problems or bug reports without the correct
Do not publish bug reports without specifying logs (logcats) or steps to reproduce the bug.
a) Logcat
b) proc/last_kmsg
(or proc/kmsg)
c) data/tombstones
d) dmesg
Device name:
OnePlus 5 (cheeseburger)
OnePlus 5T (dumpling)
Download OTA microG
dumpling
cheeseburger
+
Sign.spoofing Rom
Contributors
Exodusnick
microG Source code :
android_vendor_partner_gms
LineageOS source code :
- https://github.com/LineageOS
Kernel:
- android_kernel_oneplus_msm8998
Support for german users
forum.los-legacy.de
Telegram Group
t.me/losoneplus5
ROM OS Version: Android 13
ROM Kernel: Linux 4.4.x
Based On: LineageOS
Required firmware: OxygenOS 10.0.1
Version Information
Status: Stable
Created 04.12.2022
Last Updated 15.05.2023
Everyone is responsible for his own actions. Neither the operator of the site, nor I take responsibility for any damage to your device caused by any flash attempts.

reserve

new update Lineageos 20.0 microG see download link
Changelog 04.12.2022
- Synced with LineageOS sources
- Merged November 2022. Security update
- update bromite-WebView v108.0.5359.106
- update bromite Browser v108.0.5359.106
Changelog mircoG
-update to v0.2.26.223616
Releases · microg/GmsCore
Free implementation of Play Services. Contribute to microg/GmsCore development by creating an account on GitHub.
github.com
oneplus 5T dumpling
lineage-20.0-20221204-microG-signed-dumpling.zip
oneplus 5 cheeseburger
lineage-20.0-20221204-microG-signed-cheeseburger.zip
Upgrade to 20.0 can be installed over 19.1.
or clean
via ota will work with the next update
it is recommended to remove custom encryption pins/passwords (recommended).

chrome incompatible

nice rom

mishterqwerty said:
chrome incompatible
Click to expand...
Click to collapse
Use bomite or other.
Chrome sends too much data to Google
Chrome uses googel crap.....

Exodusnick said:
Use bomite or other.
Chrome sends too much data to Google
Chrome uses googel crap.....
Click to expand...
Click to collapse
ok thanks

I don't know if I'd run a MicroG ROM, but just out of curiosity, how's the battery when compared to any other Android 12 or 13 ROM with Google services? Is there a noticeable difference?

new update Lineageos 20.0 microG via OTa or see download link
Changelog
10.12.2022.
- Merged December 2022. security update
- Merged android 13 (TQ1A.221205.011)
December 2022 update (QPR1)
- Synced with LineageOS source
- Update bromite WebView v108.0.5359.109
- Update bromite Browser v108.0.5359.109
oneplus 5T dumpling
lineage-20.0-20221210-microG-signed-dumpling.zip
oneplus 5 cheeseburger
lineage-20.0-20221210-microG-signed-cheeseburger.zip

I'm having issues with Seedvault backup, it always fails, does it work for any of you?
I've found this but don't know if it's related : https://github.com/seedvault-app/seedvault/issues/485

Does this ROM support Face Unlock?

all google apps work? customizations are there? like themse...accent color ? fonts etc?

bonswouar said:
I'm having issues with Seedvault backup, it always fails, does it work for any of you?
I've found this but don't know if it's related : https://github.com/seedvault-app/seedvault/issues/485
Click to expand...
Click to collapse
may well be possible .
I do not use it have never used it either.

qlb1234 said:
Does this ROM support Face Unlock?
Click to expand...
Click to collapse
no only pattern and fingerprint works

roamermak said:
all google apps work? customizations are there? like themse...accent color ? fonts etc?
Click to expand...
Click to collapse
I can not answer
you have to test yourself.
do not know what app you use

The basic ones. Maps, photos, mail, chrome, note etc.

roamermak said:
The basic ones. Maps, photos, mail, chrome, note etc.
Click to expand...
Click to collapse
yes these work

new update Lineageos 20.0 microG see download link
Changelog 27.12.2022
- Synced with LineageOS sources
- default web Browser and webview back
because there are problems with the signature of bomite
web Browser
- fixed lineage updater add los-legacy OTA server
Update strings.xml · Exodusnick/[email protected]
Contribute to Exodusnick/android_packages_apps_Updater development by creating an account on GitHub.
github.com
Changelog mircoG
---
oneplus 5T dumpling
lineage-20.0-20221227-microG-signed-dumpling.zip
oneplus 5 cheeseburger
lineage-20.0-20221227-microG-signed-cheeseburger.zip
Spoiler: info please read !!
install manually,
at the next update the rom
will show up in the Lineageos Updater
the current one will then also be shown
Spoiler: info please read !!
what you have already installed here.

qlb1234 said:
Does this ROM support Face Unlock?
Click to expand...
Click to collapse
test this maybe you are lucky and it works
[11+] UniversalAuth: Face Unlock for all ROMs
UniversalAuth: Face Unlock for all ROMs This module brings face unlock (and possibly other authentication methods) to any ROM. Requirements - Xposed/EdXposed/Lsposed - Android 11, 12 or 13 DP (may also work on Android 10, but not tested)...
forum.xda-developers.com