[ROM][UNOFFICIAL][alpha] LineageOS 17.1 for Redmi K30 5G (picasso) (20200419) - Redmi K30 5G ROMs, Kernels, Recoveries, & Other D

[ROM][UNOFFICIAL][alpha] LineageOS 17.1 for Redmi K30 5G (picasso) (20200419) - Redmi K30 5G ROMs, Kernels, Recoveries, & Other D

{
"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"
}
WARNING
DO NOT try to install this on the non-5G version of Redmi K30. This ROM is ONLY intended for Redmi K30 5G and they are NOT the same device. Their difference is more than just 5G or non-5G.
Introduction
This is an UNOFFICIAL port of LineageOS 17.1 (based on Android 10) for the device Redmi K30 5G, codenamed Picasso.
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 Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What's working
- All basic mobile phone features (Wi-Fi, Bluetooth, Cellular Data, Phone Calls, SMS, etc., incl. 5G and VoLTE)
Known Issues
- (For Chinese Users) NO Alipay / WeChat Pay fingerprint support, and no plan to add support for them. Ask Alibaba / Tencent to support the standard Android biometrics API, not me to make my ROM support their API.
- 3.5mm jack does not work for some reason. (Will be fixed in the next release) Fixed since 20200311
- Wi-Fi display is not implemented since I have no device to test it on
- VoWiFi is not tested since I have no carrier support
- No 5G toggle. You cannot disable / enable 5G support. It's on by default and it goes to 5G if it can. (Note: there seems to be a dedicated network type option now in settings - mobile network for 5G NR, but I checked AOSP source code and that's only for 5G SA, and 5G NSA still falls under LTE, not the NR type)
- CTS does not pass because xiaomi's build fingerprint is not CTS-verified. You are on your own finding a solution to this. (Hint: Magisk modules)
- (For Developers) I cannot build a working DTB image from the sources provided by Xiaomi. I do not know the exact reason and for now I'm using prebuilt DTB and DTBO images, which you can extract from the official ROM and its boot.img.
- I'm not sure if there is any other issue, but at least nothing deal-breaking for me.
Instructions (Install / Upgrade) (IMPORTANT)
Side Note: I am fully aware that there is a TWRP port for this device, however it seems to be based on a modified version of TWRP whose source code I cannot find. The official TWRP repository (that I can see) does not even support Android 10 dynamic partitions yet, let alone porting it to this device. Of course it is possible that the author of that TWRP port has access to some internal testing version of TWRP, but since I cannot access the source code either way, I cannot do tests on the TWRP port. The LineageOS recovery I ported is adjusted specifically for this ROM and I have only tested the ROM on my LineageOS recovery port. If you choose to use the TWRP port, you are on your own, and do not ask me for problems you may encounter by using that port.
1. Install LineageOS 17.1 Recovery following my guide in the other thread (https://forum.xda-developers.com/re...covery-lineageos-recovery-17-1-redmi-t4059879), DO NOT use TWRP because it will NOT work for devices with dynamic partitions.
2. Reboot to LineageOS Recovery, wipe all data (skip if you are upgrading) (BACKUP ALL YOUR DATA TO A COMPUTER BEFORE FLASHING)
3. Flash required OFFICIAL MIUI version via adb sideload before flashing LineageOS 17.1. (consult the Downloads section for the corresponding MIUI version required for each LineageOS release)
- Flash OFFICIAL, not Xiaomi.eu or any other modified version.
- You can skip this step if you already have the required MIUI firmware + vendor version flashed before (e.g. if you upgrade from an older release of my LineageOS port and I did not change the required MIUI version)
- You can choose to try installing LOS on non-tested MIUI versions, though they are not tested so expect some hiccups or even disasters.
- DO NOT just flash the firmware of the required MIUI version. Always flash the full MIUI ROM (no additional wiping needed if you do not actually boot into MIUI). This ROM depends on the vendor partition provided by MIUI to work. You will need to flash at least the firmware PLUS the vendor and odm partition images of its required MIUI version for the ROM to actually work.
4. Flash LineageOS 17.1 zip via adb sideload
5. Reboot to Recovery (If you want to install Magisk or OpenGAPPS or both, else just reboot to system
6. Select "Mount /system" in the rebooted Recovery, ignore any error that may pop up on the screen
7. If you would like to, install Magisk (you MUST use a version later than or equal to 20.4)
8. If you would like to, install patched OpenGAPPS zip (available in Downloads section. You MUST use the patched OpenGAPPS for now.)
9. Reboot and enjoy. Magisk may cause your phone to double-boot (i.e. auto-reboot after the logo disappears) on first boot. If your phone boots up the second time then it will be fine.
Downloads
20200419: https://mega.nz/file/LAJjCYDT#L1Rd-WFJQ7SaU3vfAxU2y7AJsfH9qZ3fSAKMTQhgPWM
(MIUI firmware / vendor version tested on: miui_PICASSO_V11.0.11.0.QGICNXM_65ec88895f_10.0)
Changelog:
- Updated LOS source (April patch)
- You can now install the OFFICIAL version of Magisk >= 20.4 without modification
20200311: https://mega.nz/#!iB53SIKQ!ewdfMNFHmHjOemDDuYcgQO2t1KgrB9hx6YXYAdLKxU4
(MIUI firmware / vendor version tested on: miui_PICASSO_V11.0.11.0.QGICNXM_65ec88895f_10.0)
Changelog:
- Fixed 3.5mm jack support
- Lowered minimum allowable brightness to match the auto brightness curve
- Synchronized LineageOS 17.1 March Security Patch update
20200307: https://mega.nz/#!KQ5jkbAQ!dJspI92ls3BiVGk8FIGbVf4b4QBkwaaLUUr_NKX020A
(MIUI firmware / vendor version tested on: miui_PICASSO_V11.0.11.0.QGICNXM_65ec88895f_10.0)
Patched OpenGAPPS 20200306 (2): https://mega.nz/#!2EwVzAJR!NmBbO1_ao5ziyup6UVx64lZK06_VGNXSsFDA9T4sOO0
(Changelog: added `sync` after flashing to ensure everything is actually written to /system; also added a flag to `tar` to ignore creation times because that seems to break sometimes in our recovery)
Patched OpenGAPPS 20200306: https://mega.nz/#!2NgHXL6T!Z7J6AbJ7i4y9AuflIF0v_7KLbAO8XVV4ACsk13oz380
(What's patched: the `busybox` included in OpenGAPPS cannot mount the system partition as Read-Write in LineageOS Recovery for some reason. I edited the install script to use the `mount` command provided by the recovery instead of busybox. Also I removed the unmounting at the end of installation since it seem to stall the whole recovery, which means you will have to flash OpenGAPPS at the very last of your flashing process.)
XDA:DevDB Information
LineageOS 17.1 for Redmi K30 5G, ROM for the Redmi K30 5G
Contributors
PeterCxy
Source Code: https://github.com/PeterCxy/android_device_xiaomi_picasso
ROM OS Version: Android 10
Version Information
Status: Alpha
Created 2020-03-08
Last Updated 2020-03-08

I've been trying to compile the os from your device tree these days...now it's a waste of time
Anyway, I've followed you on GitHub. Thank you for doing so much!

zhufucdev said:
I've been trying to compile the os from your device tree these days...now it's a waste of time
Anyway, I've followed you on GitHub. Thank you for doing so much!
Click to expand...
Click to collapse
Sorry for that, you need some additional patches in LineageOS to actually build it successfully (you can search for patches by me on LOS gerrit: https://review.lineageos.org/q/owner:peter%40cxy.moe). Also I haven't uploaded the prebuilt DTB / DTBO image in my device tree. You will need to extract those on your own (or maybe you can help me figure out why the official open-source version does not work)

PeterCxy said:
Sorry for that, you need some additional patches in LineageOS to actually build it successfully (you can search for patches by me on LOS gerrit: https://review.lineageos.org/q/owner:peter%40cxy.moe). Also I haven't uploaded the prebuilt DTB / DTBO image in my device tree. You will need to extract those on your own (or maybe you can help me figure out why the official open-source version does not work)
Click to expand...
Click to collapse
I'm sorry but I am basically a noob on ROM porting. I'm only familiar with some basic linux commands and Android developing.

Hi, there! There is something I can't figure out:
Is there any checksums for ROM?
BTW, is there any force encryption feature in LineageOS?
However, thanks for your ROM.

RiverYKB said:
Hi, there! There is something I can't figure out:
Is there any checksums for ROM?
BTW, is there any force encryption feature in LineageOS?
However, thanks for your ROM.
Click to expand...
Click to collapse
No checksum, but since Mega.nz uses end-to-end-encryption it should do checksum on its own. Also you can verify the package against testkeys.
Force encryption is of course enabled by default.

PeterCxy said:
No checksum, but since Mega.nz uses end-to-end-encryption it should do checksum on its own. Also you can verify the package against testkeys.
Force encryption is of course enabled by default.
Click to expand...
Click to collapse
I'm just worrying about my downloaded ROM. Because you know some of E2EE file send platforms (such as Mega.nz) is being blocked by Chinese Gov. ?So I have to download with VPN.
But it's just fine.

Do not try it on the non 5G K30, oh ok means now I definitely have to try it.

Ya_SG said:
Do not try it on the non 5G K30, oh ok means now I definitely have to try it.
Click to expand...
Click to collapse
You may have better luck trying a K20 ROM on non-5G K30 than trying this one. The non-5G K30 shares the same kernel source tree with K20 instead of K30 5G. (of course, existing K20 kernels and thus ROMs do not even support dynamic partitions, so you would probably not be able to boot either way)

Hi!
I know I'm a really noob, but I ran into a problem.
So before I flash LineageOS, my /sdcard and /data is already encrypted.
And I backed my files to /sdcard, then I wiped /data and flashed LineageOS.
I can boot to LineageOS properly now, but I can't access my backup files in /sdcard, it's all garbled.
Is there any way to help?
Thank you very much.

RiverYKB said:
Hi!
I know I'm a really noob, but I ran into a problem.
So before I flash LineageOS, my /sdcard and /data is already encrypted.
And I backed my files to /sdcard, then I wiped /data and flashed LineageOS.
I can boot to LineageOS properly now, but I can't access my backup files in /sdcard, it's all garbled.
Is there any way to help?
Thank you very much.
Click to expand...
Click to collapse
looks like you have wiped the encryption keys for some reason. Unfortunately, there's nothing I can do to help in this case.

RiverYKB said:
Hi!
I know I'm a really noob, but I ran into a problem.
So before I flash LineageOS, my /sdcard and /data is already encrypted.
And I backed my files to /sdcard, then I wiped /data and flashed LineageOS.
I can boot to LineageOS properly now, but I can't access my backup files in /sdcard, it's all garbled.
Is there any way to help?
Thank you very much.
Click to expand...
Click to collapse
Hi RiverYKB
The point I guess is to decrypt the data partition, which can be easily done using a TWRP recovery. So I suggest flashing TWRP via fastboot with your computer. You should be able to decrypt your data with the password set before lineage os was flashed.

Updated 20200311

PeterCxy said:
Updated 20200311
Click to expand...
Click to collapse
it looks like bootloop after flash 0311 version, logcat file below
htdeletemetps://drive.google.com/file/d/1INO9nNnEyR_JxmJRvZzhNrOVfWrDIuwv/view?usp=sharing

Cedric1223 said:
it looks like bootloop after flash 0311 version, logcat file below
htdeletemetps://drive.google.com/file/d/1INO9nNnEyR_JxmJRvZzhNrOVfWrDIuwv/view?usp=sharing
Click to expand...
Click to collapse
Your issue seems gapps-related. Make sure you flash my patched version of gapps, not the official version. Did you upgrade to 0311 from 0307 or just flash 0311? If you upgraded, make sure you re-flash gapps after the upgrade.

I will try when next update comes, thank you for your great rom port
PeterCxy said:
Your issue seems gapps-related. Make sure you flash my patched version of gapps, not the official version. Did you upgrade to 0311 from 0307 or just flash 0311? If you upgraded, make sure you re-flash gapps after the upgrade.
Click to expand...
Click to collapse

This rom working on poco x2 4g?

fromjeet said:
This rom working on poco x2 4g?
Click to expand...
Click to collapse
of course not

It looks like if I set a password for Hotspot, other devices can not connect this hotspot
if no password for hotspot, it works perfectly

Thanks for your ROM since I have been using it for a couple of days with no critical problem found. However,
1. Since 5G NSA falls under LTE, is it possible to make it displaying "NR" or something else to indicate that the phone is on 5G network? If impossible, is there any other ways to know whether the phone is on 5G or not?
2. Is there a working root solution for it?
Thank you for your time and effort

Related

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

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.

LineageOS 16.0 - Xiaomi Mi A2 Lite [ENFORCING]

# Reserved

# Reserved 2

Thanks!!!!!!

Thanks a lot!, I am already on january stock rom with twrp and rooted, with magisk modules.
Should i restart with fresh rom flash, or i can just wipe and flash?.

Does this rom have los updater working?

just wipe /data and /system and install
Txatxiquesi said:
Thanks a lot!, I am already on january stock rom with twrp and rooted, with magisk modules.
Should i restart with fresh rom flash, or i can just wipe and flash?.
Click to expand...
Click to collapse
---------- Post added at 02:53 PM ---------- Previous post was at 02:52 PM ----------
los updater is for official rom , this rom is unofficial so no... but is not a problem for update after flash new zip in twrp and reboot
Moemen Gaber said:
Does this rom have los updater working?
Click to expand...
Click to collapse

Moemen Gaber said:
Does this rom have los updater working?
Click to expand...
Click to collapse
Being it's still in a testing phase I doubt it.but not 100% sure

Will this ever support custom kernel?
I need color calibration to remove yellowish tint of my phone. And to some who will say im on reading mode or etc. NO, my default lcd is EBBG, its warm tone by default.

camera2 API works? are this tom can use oreo vendor?

leitseleac said:
Will this ever support custom kernel?
I need color calibration to remove yellowish tint of my phone. And to some who will say im on reading mode or etc. NO, my default lcd is EBBG, its warm tone by default.
Click to expand...
Click to collapse
1. Open the kernel ZIP file
2. Copy module/system/vendor/lib/modules/wlan.ko to module/system/lib/modules
3. Flash the kernel.
But you don't need a custom kernel to change the hue, there's an option for that in LOS settings.

davidrocher said:
1. Open the kernel ZIP file
2. Copy module/system/vendor/lib/modules/wlan.ko to module/system/lib/modules
3. Flash the kernel.
But you don't need a custom kernel to change the hue, there's an option for that in LOS settings.
Click to expand...
Click to collapse
Does it have RGB values adjuster

CreateYourDream said:
camera2 API works? are this tom can use oreo vendor?
Click to expand...
Click to collapse
Gcam does not work. LOS can only be installed on the vendor pie.

during flashing it appears: updater process ended with error 1. I think it's something at boot level if I'm not mistaken. I tried flashing the boot stock and then the rom, but it still gives me error 1. How do I solve it?

Could you explain how to correctly install the rom together with the gapps? he made me hard brick which I had to solve with test points after doing a clean installation together with the gapps "open_gapps-arm64-9.0-pico-20190406"

I'm having trouble decrypting my phone on TWRP, did anyone manage to do this?

Hakkinan said:
I'm having trouble decrypting my phone on TWRP, did anyone manage to do this?
Click to expand...
Click to collapse
You have to wipe system, data and cache

Pupo_28 said:
You have to wipe system, data and cache
Click to expand...
Click to collapse
Already did that, i'm having trouble decrypting after i've installed LOS (it was said that the rom supports HW encryption and the new TWRP was supposed to fix this problem).

Hakkinan said:
Already did that, i'm having trouble decrypting after i've installed LOS (it was said that the rom supports HW encryption and the new TWRP was supposed to fix this problem).
Click to expand...
Click to collapse
Owh, sorry then I thought you referred to the password asked to let it mount the storage

help error 1 in twrp, what do i do ?

[ROM][UNOFFICIAL][RAMDISK][11] LineageOS 18.1 for Galaxy S10e/S10/S10+/S10 5G Exynos

Requirements:
Any Q or R based firmware installed on your device.
Pre-Install Instructions
Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.
Connect the device to a Wi-Fi network.
Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu
From within the Developer options menu, enable OEM unlock.
Power off the device, and boot it into download mode:
With the device powered off, hold Volume Down + Bixby and connect USB cable to PC.
Now, click the button that the onscren instructions coorelate to “Continue” and/or “Unlock Bootloader”.
Your device will reboot, you may now unplug the USB cable from your device.
The device will demand you format userdata, please follow the onscreen instructions to do so.
Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About” menu, and verify that “OEM Unlock” is still enabled in the “Developer options” menu.
Installing LineageOS for the first time
Flash lineage recovery
Only the provided lineage recovery will be supported,
using TWRP might result in a possible data loss!!
If using Odin rename the lineage recovery image for your model to recovery.img and add it to a .tar archive using e.g 7zip.
If using Heimdall use: heimdall flash --RECOVERY recovery.img --no-reboot
Boot lineage recovery
IMPORTANT: Do not boot into system again before booting recovery, or system will restore stock recovery!
If using Odin untick auto-reboot before flashing.
After flashing reboot by pressing Volume Down and Power for approximately 7 seconds,
immediately hold Volume Up, Bixby and Power to boot recovery
IMPORTANT: As of OneUI 3 your device needs to be connected to a PC via USB cable in order to be able to
boot recovery via Volume Up, Bixby and Power.
Factory reset using Factory reset -> Format data/factory reset
Warning: Unlike TWRP this will also erase internal storage!
Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
Then run adb sideload <path to your lineage.zip> on your PC
Optional:
Sideload GApps and magisk by repeating above step
with their zip/apk
Magisk
As this ROM has a working ramdisk sideloading the magisk apk is enough, just as it is
on every other device, no bootimage with magisk included or installing to recovery is needed!

Features
SELinux enforcing
AES-256-XTS FBE encryption
Latest Linux 4.14.x kernel
All cameras are working
Ramdisk is working
Dolby atmos is working
Known issues
VoLTE/VoWiFi
You tell me

Thanks for providing sources and the doing the hardwork to bring up the device, could you also provide what firmware version is required?
Also a simple guide for flashing firmware, would be helpful.

mcgi5sr2 said:
Thanks for providing sources and the doing the hardwork to bring up the device, could you also provide what firmware version is required?
Also a simple guide for flashing firmware, would be helpful.
Click to expand...
Click to collapse
Both Q and R firmwares should work
I'll add that and a guide for updating firmware later

Thank you so much for your work!
Can you provide a little more information about what's working and what bugs people might expect? I believe many are wondering about SELinux status and camera (quality and if all are usable).

DerSteppo said:
Thank you so much for your work!
Can you provide a little more information about what's working and what bugs people might expect? I believe many are wondering about SELinux status and camera (quality and if all are usable).
Click to expand...
Click to collapse
Sure I can add that too, SELinux is enforcing and all cameras are working (on beyond1lte at least)

Is this the new version of Modpunk's Lineage OS 17.1, so with selinux enforced and encrypted?

counti said:
Is this the new version of Modpunk's Lineage OS 17.1, so with selinux enforced and encrypted?
Click to expand...
Click to collapse
This is based on new trees but indeed reuses some stuff from old whatawurst trees.
But yes it's also FBE encrypted and enforcing.

Linux4 said:
Sure I can add that too, SELinux is enforcing and all cameras are working (on beyond1lte at least)
Click to expand...
Click to collapse
Thank you so much and keep up the great work!

Linux4 said:
This is based on new trees but indeed reuses some stuff from old whatawurst trees.
But yes it's also FBE encrypted and enforcing.
Click to expand...
Click to collapse
Is it possible to upgrade from Modpunk's Lineage OS 17.1? With TWRP from Modpunk?

counti said:
Is it possible to upgrade from Modpunk's Lineage OS 17.1? With TWRP from Modpunk?
Click to expand...
Click to collapse
No, sorry
And TWRP won't be supported at all here, see Post #2

Linux4 said:
No, sorry
And TWRP won't be supported at all here, see Post #2
Click to expand...
Click to collapse
But Lineage Recovery has no backup function right? that's a pity, How do you make backups?

counti said:
But Lineage Recovery has no backup function right? that's a pity, How do you make backups?
Click to expand...
Click to collapse
Do it with some app like https://f-droid.org/en/packages/dk.jens.backup/ ?
Or disable FBE encryption if you are fine with that and use TWRP ...
As long as FBE is enabled you'll eventually corrupt your /data partition by using TWRP.

is it possible to use samsung camera on aosp roms? i have s10e unfortunately can't focus on zgcam and it has color shifts in some cases. i want to flash aosp but cant find a proper camera app

hi_s10e said:
is it possible to use samsung camera on aosp roms? i have s10e unfortunately can't focus on zgcam and it has color shifts in some cases. i want to flash aosp but cant find a proper camera app
Click to expand...
Click to collapse
Not possible to use Samsung camera on any AOSP ROMS unfortunately

@Linux4 Thanks for you nice work, really appreciate it.
I was waiting for an update on Modpunks 17.1 version. Now it seams it is dead and no official LineageOS builds exist to regularly update that version. It's a bit annoying to format and set up the OS all over again every half a year or so. So do you intend to push your work to become an official version?

wora92 said:
@Linux4 Thanks for you nice work, really appreciate it.
I was waiting for an update on Modpunks 17.1 version. Now it seams it is dead and no official LineageOS builds exist to regularly update that version. It's a bit annoying to format and set up the OS all over again every half a year or so. So do you intend to push your work to become an official version?
Click to expand...
Click to collapse
I'm thinking about doing it in the future, but can't promise anything

cgirerd said:
Not possible to use Samsung camera on any AOSP ROMS unfortunately
Click to expand...
Click to collapse
thank you

is there anyway to make volte work ?

[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

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