[ROM][10.0][User build][Signed] Lineage-17.1-X00TD-Asus Zenfone Max Pro M1

Search This thread

Rasyad

Member
Jun 13, 2014
16
6
installed lineage-17.1-20210304-X00TD-user-signed build since gets uploaded.
I didn't see any audio difference, but everything working great as previous stable build, no issue found so far.
Well, I think this build is rock stable 😁
 

Attachments

  • Screenshot_20210304-044246_Settings.png
    Screenshot_20210304-044246_Settings.png
    153.1 KB · Views: 41
  • Screenshot_20210304-061030_Music.png
    Screenshot_20210304-061030_Music.png
    890.5 KB · Views: 44
  • Screenshot_20210304-043325_Settings.png
    Screenshot_20210304-043325_Settings.png
    238.2 KB · Views: 39

Orion281

Member
Sep 15, 2015
37
14
Check audio distortion at higher volumes. Previous builds has this issue. 20210304 uses CAF audio.
I flashed the latest experimental build but didn't find any noticeable difference in the sound output. Speaker output is as low as it had been on previous builds. One more thing that I've encountered in this build is that the sound output during calls is very loud and distorted. I lowered the volume to minimum and still could hear everything as if the speaker was on. I hope this helps. Thanks.
Edit: I found audio distortions at high volumes only during calls not while listening music or watching something. I may be wrong though. Someone else has to confirm this.
 
Last edited:
  • Like
Reactions: [email protected]

[email protected]

Senior Member
  • Sep 18, 2018
    564
    361
    Pennadam Town Tamil Nadu
    I flashed the latest experimental build but didn't find any noticeable difference in the sound output. Speaker output is as low as it had been on previous builds. One more thing that I've encountered in this build is that the sound output during calls is very loud and distorted. I lowered the volume to minimum and still could hear everything as if the speaker was on. I hope this helps. Thanks.
    Edit: I found audio distortions at high volumes only during calls not while listening music or watching something. I may be wrong though. Someone else has to confirm this.
    Also check bluetooth audio .

    For Testers: Also check bugs on clean flash . After thorough testing I will update OTA build soon with security patch.
     
    • Like
    Reactions: Orion281
    Aug 17, 2018
    15
    0
    So, just to get this straight, because I'm kind of confused by the intro of this thread. I'm on the latest WW stock Pie release. In order to flash this ROM, while maintaining Widevine L1 certification, I do have to unluck the bootloader in order to flash TWRP or similar first?

    Can someone just list the steps involved?
     

    [email protected]

    Senior Member
  • Sep 18, 2018
    564
    361
    Pennadam Town Tamil Nadu
    So, just to get this straight, because I'm kind of confused by the intro of this thread. I'm on the latest WW stock Pie release. In order to flash this ROM, while maintaining Widevine L1 certification, I do have to unluck the bootloader in order to flash TWRP or similar first?

    Can someone just list the steps involved?
    You need to backup persist partition before flashing custom rom. Backup guide is mentioned in this thread. So you can save widewine L1 certification.
    So, just to get this straight, because I'm kind of confused by the intro of this thread. I'm on the latest WW stock Pie release. In order to flash this ROM, while maintaining Widevine L1 certification, I do have to unluck the bootloader in order to flash TWRP or similar first?

    Can someone just list the steps involved?
    You need to backup persist partition before flashing custom rom. Backup guide is mentioned in this thread. So you can save widewine L1 certification.
     
    Aug 17, 2018
    15
    0
    You need to backup persist partition before flashing custom rom. Backup guide is mentioned in this thread. So you can save widewine L1 certification.
    You must be refering to this guide: https://forum.xda-developers.com/t/guide-dump-all-partitions-and-make-complete-backup.3791202/

    So, the steps would be:

    1) Factory reset on original Pie en locked stock bootloader (to prevent issues with flashing)
    2) unlock bootloader
    3) flash custom recovery

    4) backup persist partition as stated in guide.

    5) Flash custom rom + GApps via custom recovery
    6) ?Restore persist?

    I don't really understand what the backup persist provides. Is it just a safeguard to be able to return to stock ROM and L1 certification? Am I right? What am I missing?
     

    [email protected]

    Senior Member
  • Sep 18, 2018
    564
    361
    Pennadam Town Tamil Nadu
    You must be refering to this guide: https://forum.xda-developers.com/t/guide-dump-all-partitions-and-make-complete-backup.3791202/

    So, the steps would be:

    1) Factory reset on original Pie en locked stock bootloader (to prevent issues with flashing)
    2) unlock bootloader
    3) flash custom recovery

    4) backup persist partition as stated in guide.

    5) Flash custom rom + GApps via custom recovery
    6) ?Restore persist?

    I don't really understand what the backup persist provides. Is it just a safeguard to be able to return to stock ROM and L1 certification? Am I right? What am I missing?
    Actually backup guide is a suggestion from a user from asus zenfone max pro M1 community group.

    First thing i want to make clear that I haven't tested this backup method.

    Explanation:

    From stock android pie.

    1. For backup. You need to unlock bootloader in stock rom and backup persist partition.
    2. Then you will flash custom rom through twrp and will lose your L1 certification to L3.
    3. If you try stock rom again by fastboot you will stay in L3 certification. To solve this you need flash persist partition to get L1.
    All this backup only works on android pie.

    From android 10 stock rom.

    1. Unlocking bootloader from stock android 10 will lose your widewine L1 by default from very first step. No way to recover.
     
    Aug 17, 2018
    15
    0
    Actually backup guide is a suggestion from a user from asus zenfone max pro M1 community group.

    First thing i want to make clear that I haven't tested this backup method.

    Explanation:

    From stock android pie.

    1. For backup. You need to unlock bootloader in stock rom and backup persist partition.
    2. Then you will flash custom rom through twrp and will lose your L1 certification to L3.
    3. If you try stock rom again by fastboot you will stay in L3 certification. To solve this you need flash persist partition to get L1.
    All this backup only works on android pie.

    From android 10 stock rom.

    1. Unlocking bootloader from stock android 10 will lose your widewine L1 by default from very first step. No way to recover.
    OK. So, flashing custom ROM will ALWAYS result in (temporary) loss of L1 certification. The Pie based persist partition backup should be able to get you L1 certification again, if you decide to return to stock Pie.

    OK. Makes sense I guess.
     

    [email protected]

    Senior Member
  • Sep 18, 2018
    564
    361
    Pennadam Town Tamil Nadu
    OK. So, flashing custom ROM will ALWAYS result in (temporary) loss of L1 certification. The Pie based persist partition backup should be able to get you L1 certification again, if you decide to return to stock Pie.

    OK. Makes sense I guess.
    OK. So, flashing custom ROM will ALWAYS result in (temporary) loss of L1 certification. The Pie based persist partition backup should be able to get you L1 certification again, if you decide to return to stock Pie.

    OK. Makes sense I guess.
    Widewine L1 certification is only available on stock rom with locked bootloader.
    As mentioned in thread, unlocking bootloader from android10 will lose your L1 permanently. Reverting to stock rom wont help. Only if you did persist backup on android pie will help.
     

    Top Liked Posts

    • There are no posts matching your filters.
    • 2
      These issue also noticed in stock ROM.
      I see. Well, that's a shame. Your build is pretty much the only Android 10 ROM with working enforcing SELinux.
      Thank you for the clarification.
      2
      Another one kernel for testing : 4.4.263 based on https://github.com/wimbiyoas/msm-4.4/commits/master
      - NFC works , battery should also like with pixel one. You could check other issues too.


      @[email protected] I tested some kernels for your 17.1 . I think it looks ok. If you want I can share repo with changes but you need to decide which kernel we will use. The best one in my opinion is the pixel one because have qcom drivers released 2020 instead of 2017. Should be much more stable but will require update vendor part for example for NFC.
      2
      I can see that test build getting worse and problem with battery charging still occur. I found for now howto solve problem with battery charging on the current builds.:
      - install magisks
      - install plugin acc in the magisks
      - restart phone
      - install from fdroid the accd app and add root access only one time
      - reconfigure acc via accd and set disable charing on the 100%.
      - restart phone
      - uninstall accd
      - remove in the magisks root access for all apps.

      Maybe its a good idea add acc into the build?

      best regards,
      2
      Only for volunteer testers

      To check OTA property of lineage-18.1 over lineage-17.1.
      Download manually and update.Before installing wipe cache,system and vendor in twrp

      lineage-18.1-20210413-X00TD-user-signed.zip
      2
      Can I update the ROM if I'm encrypted.
      Chances are you are not encrypted if you are human, but the /data partition in your smartphone probably is. And yes, it's safe to update using updates received by OTA.
    • 6
      hero.png


      About LineageOS

      Lineage-17.1-X00TD-Asus Zenfone Max Pro M1

      Build type : UNOFFICIAL


      Build and signed by @[email protected] | Rajesh R

      Disclaimer : ROMs are built for development purpose only. Use at your own risk.

      This ROM completely compiled on lineage source code and with minimum workarounds for a successful build. Builds are signed with release-keys.Before installing, refer instructions and changelog for each builds.


      About build variants

      ROM-Signed release key-user build

      lineage-17.1-20210404-X00TD-user-signed

      Features
      *Gesture navigation android 10.
      *Enforcing selinux and user build properties
      * Certified device status under google play
      * SafetyNet Test is passed
      * Smooth ROM experience


      Instructions

      Backup procedure and precaution information


      Must read before unlocking bootloader and flashing custom ROM



      Some explanation regarding the whole widewine L1-L3-Qbeta etc ( Info @ https://t.me/ASUSX00TD from a member )

      Starting from Q builds Asus has begun wiping DRM keys if bootloader is unlocked on that build, which is actually default behavior among most other OEMs like pixels, oneplus. Flashing Q builds (Stock beta 1 or latest) or custom ROM on unlocked bootloader through TWRP will permanently loose their L1 certification. widewine keys will be wiped by firmware itself as it detects unlocked bootloader. This also explains why some people, who flashed previous stock Q beta before on locked bootloader, even though first stock Q beta had L3 which means they hadn't fixed L1 on that beta that time , retained their L1/DRM keys on reverting to pie via downgrade zip provided by asus. So in conclusion Asus Q builds/custom ROM will wipe your DRM keys if flashed on Unlocked bootloader. Flashing on locked bootloader shouldn't be any problem!

      Also those who have their persist partition backed up in pie should have no problem restoring their DRM keys in case thet got wiped by Q firmware/builds

      How to Backup Persist ?

      Dump all partitions and make complete backup | Partition layout and structure

      Recovery method

      use recoveries which support persist partition backup (eg. Orangefox)
      Go to recovery > Backup > tick persist > backup > store it safe somewhere with multiple copies.

      How to Restore Persist ?

      Go to recovery > Restore menu > select backup > tick persist partition > Restore (process similar/different for different recoveries)



      Upgrading to LineageOS 17.1

      1. Make a backup of your important data
      2. Download the build and also Gapps.
      3. Download proper addons packages GApps for Android 10/Lineage OS 17.1
      4. Make sure your recovery and firmware are up to date
      5. For clean flash, Format your system,vendor,data and cache partition partition to install ROM and Gapps.
      6. For installing updates format system,vendor and cache partition. keep data partition intact to flash ROM and Gapps.

      Secure ROM experience

      Avoid permissive selinux and rooting methods for secure ROM experience.
      Refer
      1. Root & SELinux Risks
      2. TWRP password protection
      3. TWRP encryption




      Screenshots


      omklsMo.jpg


      JoXTMZ8.jpg




      Upcoming builds ( Only for volunteer testers )


      lineage-17.1-20210417-X00TD-user-signed.zip
      * Check if audio distortion present at peak volume.


      lineage-18.1-20210413-X00TD-user-signed.zip

      * Enforcing selinux and user build properties
      * Release-key signed.
      * Android Verified Boot (AVB)

      To test any ROM

      Requirements:


      Windows/linux Pc
      adb drivers
      Usb cable.

      Steps to take log:

      1. Install adb drivers in pc and enable usb debugging mode in phone. Also enable root debugging if needed.
      2. Connect phone through usb and type the command "adb logcat -d>logcat.txt" in adb command window.You can choose any name you want for txt file. If needed give admin privilege for adb command window.
      3. This procedure can also be used to watch occurance of bugs at realtime by connecting phone at adb mode to pc.

      Steps to take boot log:


      1. Make sure adb is enabled in phone. Connect the phone in usb mode to pc and open adb command window.
      2. Switch off the phone and type "adb logcat -d>bootlog.txt".
      3. Initially "waiting for the device" message is noticed on adb command window and switch on the phone now. once the device powers on, boot log is recorded.

      log text files are stored in location where adb drivers are installed.

      Note : Test builds are released here and intended to test upcoming fixes and features.




      Source Code

      Kernel source code : https://github.com/SagarMakhar/android_kernel_asus_sdm660

      Kernel developer credits : @SagarMakhar


      Credits

      Google's AOSP Project.
      Lineage OS for the source code and The Open GApps Project.
      Contribute to Lineage OS at https://paypal.me/LineageOS
      Contribute to Gapps at https://www.paypal.com/donate/?toke...EScTbkNmciIDl9n5LyDW&country.x=US&locale.x=US
      Thanks to developers and their contribution on custom ROM development for Asus zenfone max pro M1. Thanks @Patching.Unconditionally, @patkk for testing builds.

      Special thanks for the build server admin and @abhishekt295 , TheButti for upload server.


      It's all free, but donations are welcome
      Donations will be contributed to server maintenance



      84rwGCO.jpg

      shThQL3.jpg


      Support developers on their respective threads.

      Feedback and bug reports are welcome.

      Kindly use english language on comment section
      5
      Changelog

      19. OTA update : lineage-17.1-20210404-X00TD-user-signed
      * KSM tunning
      * Removal of SoterService

      18. OTA update : lineage-17.1-20210327-X00TD-user-signed
      * VoLTE icon support on status bar.
      * Updated audio drivers.
      * KSM tunning.

      17. OTA update : lineage-17.1-20210306-X00TD-user-signed
      * CAF audio.
      * Updated audio configs from stock 10 release.

      16. OTA update : lineage-17.1-20210204-X00TD-user-signed
      * Kernel updates
      * Sepolicy updates on enforcing selinux.
      * Fingerprint biometrics fixes.
      * Safetynet fixes.

      15. OTA update : lineage-17.1-20210103-X00TD-user-signed
      * Sepolicy updates on enforcing selinux.
      * Fingerprint biometrics fixes
      * MusicFX Equalizer (Download optional add-on )

      14. OTA update : lineage-17.1-20210101-X00TD-user-signed (Optional download)
      *Permissive selinux .

      13. Build name :lineage-17.1-20201229-X00TD-user-signed
      * OTA support through lineage updater.
      * Sepolicy cleanup
      * MusicFX Equalizer (Download optional add-on )

      12. Build name :lineage-17.1-20201215-X00TD-user-signed
      * Security patch update
      * Updated Fingerprint driver from asus android 10 beta.

      11. Build name :lineage-17.1-20201112-X00TD-user-signed
      * Security patch update
      *Added Fingerprint driver

      10. Build name : lineage-17.1-20201101-user-signed
      * Safetynet fixes and sepolicy updates.

      9. Build name : lineage-17.1-20201017-user-signed
      Status : Working fine
      Bugs: Fingerprint missing

      8. Build name : lineage-17.1-20201015-user-signed
      *Charging current restored to Stock values.
      * Improvements in battery backup.
      * Camera2api support for snap camera.
      * Ambient display
      * Scoped storage related fixes.
      * Dirty flash Supported over lineage-17.1-20201005-X00TD-user-signed build
      Status : Working fine

      7. Build name : lineage-17.1-20201005-user-signed
      * Enforcing selinux and user build properties
      * Certified device status under google play
      * SafetyNet Test is passed
      * Dirty flash supported over lineage-17.1-20201003/20200927-userdebug-signed builds
      Status : Working fine

      6 .Build name : lineage-17.1-20201003-userdebug-signed
      * Enforcing selinux
      * Certified device status under google play
      * SafetyNet Test is passed
      * Dirty flash supported over lineage-17.1-20200927-userdebug-signed
      Status : Working fine

      5 .Build name : lineage-17.1-20200927-userdebug-signed
      * Permissive boot
      Status : Working fine

      4. Build name : lineage-17.1-20200926-userdebug-signed
      * Permissive boot
      Status : booted but no display

      3. Build name : lineage-17.1-20200925-user/userdebug-signed
      Status : bootloop

      2. Build name : lineage-17.1-20200924-user/userdebug-signed
      Status : bootloop

      1. Build name : lineage-17.1-20200923-X00TD-user-signed
      * Lineage-17.1-20200923 | Android10_r41
      * release key user build
      * Status : Experimental release-not booting
      5
      OTA update : lineage-17.1-20210204-X00TD-user-signed

      * Kernel updates
      * Sepolicy updates on enforcing selinux.
      * Fingerprint biometrics fixes.
      * Safetynet fixes.
      * MusicFX Equalizer (Download optional add-on )

      Dirty flash supported over lineage-17.1-20210103-X00TD-user-signed
      5
      Sir, Lineage is the king of ROM. Can you please make it to the official release?
      Sure. I try to apply for official lineage.
      2
      [email protected] Fantastic ROM but charging is super slow? I clean flashed over Stock 087.
      Please help!
      View attachment 5219357
      View attachment 5219357
      I used stock values for battery and charging. I wont recommend fast charging support. Fast charging is safe only when it comes in stock. Otherwise it affects battery life.
    Our Apps
    Get our official app!
    The best way to access XDA on your phone
    Nav Gestures
    Add swipe gestures to any Android
    One Handed Mode
    Eases uses one hand with your phone