Tester Urgently Required For A14. Please Come Forward And Help Us With Testing Part.
👍9
Kirin Kernel | EAS | 4.4
Build date: 27/10/2023
by: @nohavenames
- changelog:
• ARM: dts: clean up <efficiency>
• msm_thermal: decrease temp_threshold value to 60->50
• ARM: dts: decrease voltage & power-efficient to make better battery backup
• simple_lmk: Ignore tasks that won't free memory
• ksu: sync latest source (11335)
• compile using ZycGCC
- Download
Thanks To:
@redmi4primee for donating & testing
Follow: @ASUSMaxProM2
Join: @ZenfoneMaxProM2Official
#kernel #a13 #a10 # a11 #a12 #eas #4.4
Build date: 27/10/2023
by: @nohavenames
- changelog:
• ARM: dts: clean up <efficiency>
• msm_thermal: decrease temp_threshold value to 60->50
• ARM: dts: decrease voltage & power-efficient to make better battery backup
• simple_lmk: Ignore tasks that won't free memory
• ksu: sync latest source (11335)
• compile using ZycGCC
- Download
Thanks To:
@redmi4primee for donating & testing
Follow: @ASUSMaxProM2
Join: @ZenfoneMaxProM2Official
#kernel #a13 #a10 # a11 #a12 #eas #4.4
👍9❤2🔥1👏1
Kirin Kernel | EAS | 4.4 | eleveñ
Build date: 06/12/2023
by: @nohavenames
- changelog:
- Download
- Donate
note: - do not share direct file
Follow: @ASUSMaxProM2
Join: @ZenfoneMaxProM2Official
#kernel #a13 #a10 # a11 #a12 #eas #4.4
Build date: 06/12/2023
by: @nohavenames
- changelog:
• drivers/misc: Introduce kernelspace battery saver mode
• drivers/cpufreq: disable boosting if batterysaver is active
• qpnp-smb2: increase charging val
• fs: Gain 30% Linux Disk performance
• kernel: Introduce mm-le9ec
• sync new ksu source (11384)
• builded with ZyC clang-18
• introduce BORE (Burst-Oriented Response Enhancer) CPU Scheduler
- Download
- Donate
note: - do not share direct file
Follow: @ASUSMaxProM2
Join: @ZenfoneMaxProM2Official
#kernel #a13 #a10 # a11 #a12 #eas #4.4
👍10🔥4❤3⚡1
Testers Required.
Requirements:
- PC
- Plenty of fast internet
- Patience
Requirements:
- PC
- Plenty of fast internet
- Patience
👍7
Welcome A14 4.19
Thanks to @SonicBSV @official_mocha @NotShazuxD @nem1x @Aghora_7 @themixky @IkhsanMah @z3zens @Gaurav24 And All Others Who Helped Me To Make This Possible.
Thanks to @SonicBSV @official_mocha @NotShazuxD @nem1x @Aghora_7 @themixky @IkhsanMah @z3zens @Gaurav24 And All Others Who Helped Me To Make This Possible.
🔥25👍4🎉4❤1🤩1👌1💯1
Thanks To @Owlya_1 For Donating Some Amount. I can continue now.
This media is not supported in your browser
VIEW IN TELEGRAM
TWRP | v3.7.0 | A12-A14 | 4.19
Device: Asus Zenfone Max Pro M2
Codename: X01BD
Build Date: 12-01-2024
Status: UNOFFICIAL
Build By: @RT1648 & @SonicBSV
▪️ Download
▪️ Changelogs
▪️ Credits
Follow @ASUSMaxProM2
Join @ZenfoneMaxProM2Official
#twrp #unoffical #dynmaic #retrofit
Device: Asus Zenfone Max Pro M2
Codename: X01BD
Build Date: 12-01-2024
Status: UNOFFICIAL
Build By: @RT1648 & @SonicBSV
▪️ Download
▪️ Changelogs
▪️ Credits
Follow @ASUSMaxProM2
Join @ZenfoneMaxProM2Official
#twrp #unoffical #dynmaic #retrofit
👍12👌1
CrDroid | v10.1 | A14 | 4.19 | Vanilla
Device: Asus Zenfone Max Pro M2
Codename: X01BD
Build Date: 13-01-2024
Status: UNOFFICIAL
Build By: @SonicBSV
▪️ Download: ROM || RECOVERY
▪️ Changelogs: SOURCE || DEVICE
▪️ Notes
▪️ Credits
▪️ Support
Follow @ASUSMaxProM2
Join @ZenfoneMaxProM2Official
#crDroidAndroid #X01BD #U #Unofficial #NonFBE
Device: Asus Zenfone Max Pro M2
Codename: X01BD
Build Date: 13-01-2024
Status: UNOFFICIAL
Build By: @SonicBSV
▪️ Download: ROM || RECOVERY
▪️ Changelogs: SOURCE || DEVICE
▪️ Notes
▪️ Credits
▪️ Support
Follow @ASUSMaxProM2
Join @ZenfoneMaxProM2Official
#crDroidAndroid #X01BD #U #Unofficial #NonFBE
👌11👍7❤3🔥3🥰1
#Attention #Instructions #X01BD #DYNPARTS
Attention! Before installing firmware (rom) with support for dynamic partitions, read the following annotation/instructions:
1. The dynamic partition scheme differs from the standard scheme familiar to everyone, where there are only “System” and “Vendor” sections, the dynamic partition scheme consists of a common forming section “Super”, which is divided into “System”, “SystemEXT”, “Product”, “ ODM","Vendor".
2. Early firmware (roms) with the standart partitions of the "System" and "Vendor" sections are not compatible with firmware (roms) based on a dynamic scheme, do not try to flash over it even if the firmware is the same but of a different version.
3. Switching to a dynamic partition scheme entails the loss of all data! No old backups made on the basis of a standard partition scheme will help, setting up from scratch, be prepared for this.
4. For firmware (roms) built with a dynamic partition scheme, you need to install a special recovery that supports this scheme; old recovery will not work. In the case of my builds, this is Team Win 3.7.0 12-1 recovery based on kernel 4.19 , which is presented here above on the channel.
5. For builds make with a dynamic partition scheme, only those kernels that support this very scheme are suitable (I think they will appear soon).
By installation:
1. Download recovery with support for dynamic partitions Team Win 3.7.0 12-1 based on kernel 4.19 (or possible analogues in the future).
2. Download the firmware (rom) built with dynamic partitions.
3. Back up personal data (photos, etc.) to any file storage device if necessary (I wrote about data loss above).
4. Install the recovery via "Fastboot" or through the menu of the old installed recovery, flash the img image from the recovery into the "Recovery" section.
Using “Fastboot” via a USB cable, we drop it into the root of the Linux, Windows, macOS system, open the terminal and execute “fastboot flash recovery recovery_name.img” (ignoring the quotes). You must first have all the necessary USB and ADB-Fastboot drivers installed.
5. Copy the downloaded firmware (rom) with dynamic partitions to the SD Card or internal phone memory.
6. Install using a new recovery (during the initial installation, some errors will appear, we ignore this since a normally new partition scheme has not yet been formed).
7. Without rebooting, wipe all partitions except USB-OTG, MicroSD, Internal Storage, and also execute Format Data (the one that asks for YES confirmation) and reboot into the system.
Firmware update with dynamic partitions (Retrofit Dynamic Partitions):
1. Reboot into recovery. (We have already performed the operations above, haven’t we?)
2. Flash the firmware (rom).
3. Reboot into the system.
Installing another firmware with dynamic partitions (Retrofit Dynamic Partitions):
1. Reboot into recovery.
2. Flash the firmware (rom).
3. We wipe all partitions except USB-OTG, MicroSD, Internal Storage, and also perform Format Data (the one that asks for YES confirmation).
4. Reboot into the system.
Return to standard partitions:
1. Reboot into recovery
2. Uncheck the “Settings > Unmount System before installing a ZIP” checkbox.
3. Go to Advanced > Unmap Super Devices.
4. Flash the firmware (rom) with a standard partition scheme.
5. We wipe all partitions except USB-OTG, MicroSD, Internal Storage, and also perform Format Data (the one that asks for YES confirmation).
6. Reboot into the system.
In a nutshell, what does this give us (Retrofit Dynamic Partitions):
Improved compatibility with GSI - Fans of MIUI and other similar branded firmware (roms) should rejoice, the sections are dynamic in which there are no fixed sizes, each size changes depending on needs automatically, of course within the main “Super” section (its volume).
Attention! Before installing firmware (rom) with support for dynamic partitions, read the following annotation/instructions:
1. The dynamic partition scheme differs from the standard scheme familiar to everyone, where there are only “System” and “Vendor” sections, the dynamic partition scheme consists of a common forming section “Super”, which is divided into “System”, “SystemEXT”, “Product”, “ ODM","Vendor".
2. Early firmware (roms) with the standart partitions of the "System" and "Vendor" sections are not compatible with firmware (roms) based on a dynamic scheme, do not try to flash over it even if the firmware is the same but of a different version.
3. Switching to a dynamic partition scheme entails the loss of all data! No old backups made on the basis of a standard partition scheme will help, setting up from scratch, be prepared for this.
4. For firmware (roms) built with a dynamic partition scheme, you need to install a special recovery that supports this scheme; old recovery will not work. In the case of my builds, this is Team Win 3.7.0 12-1 recovery based on kernel 4.19 , which is presented here above on the channel.
5. For builds make with a dynamic partition scheme, only those kernels that support this very scheme are suitable (I think they will appear soon).
By installation:
1. Download recovery with support for dynamic partitions Team Win 3.7.0 12-1 based on kernel 4.19 (or possible analogues in the future).
2. Download the firmware (rom) built with dynamic partitions.
3. Back up personal data (photos, etc.) to any file storage device if necessary (I wrote about data loss above).
4. Install the recovery via "Fastboot" or through the menu of the old installed recovery, flash the img image from the recovery into the "Recovery" section.
Using “Fastboot” via a USB cable, we drop it into the root of the Linux, Windows, macOS system, open the terminal and execute “fastboot flash recovery recovery_name.img” (ignoring the quotes). You must first have all the necessary USB and ADB-Fastboot drivers installed.
5. Copy the downloaded firmware (rom) with dynamic partitions to the SD Card or internal phone memory.
6. Install using a new recovery (during the initial installation, some errors will appear, we ignore this since a normally new partition scheme has not yet been formed).
7. Without rebooting, wipe all partitions except USB-OTG, MicroSD, Internal Storage, and also execute Format Data (the one that asks for YES confirmation) and reboot into the system.
Firmware update with dynamic partitions (Retrofit Dynamic Partitions):
1. Reboot into recovery. (We have already performed the operations above, haven’t we?)
2. Flash the firmware (rom).
3. Reboot into the system.
Installing another firmware with dynamic partitions (Retrofit Dynamic Partitions):
1. Reboot into recovery.
2. Flash the firmware (rom).
3. We wipe all partitions except USB-OTG, MicroSD, Internal Storage, and also perform Format Data (the one that asks for YES confirmation).
4. Reboot into the system.
Return to standard partitions:
1. Reboot into recovery
2. Uncheck the “Settings > Unmount System before installing a ZIP” checkbox.
3. Go to Advanced > Unmap Super Devices.
4. Flash the firmware (rom) with a standard partition scheme.
5. We wipe all partitions except USB-OTG, MicroSD, Internal Storage, and also perform Format Data (the one that asks for YES confirmation).
6. Reboot into the system.
In a nutshell, what does this give us (Retrofit Dynamic Partitions):
Improved compatibility with GSI - Fans of MIUI and other similar branded firmware (roms) should rejoice, the sections are dynamic in which there are no fixed sizes, each size changes depending on needs automatically, of course within the main “Super” section (its volume).
🎉10👍8❤7🔥1
CrDroid | v10.1 | A14 | 4.19 | Vanilla
Device: Asus Zenfone Max Pro M2
Codename: X01BD
Build Date: 14-01-2024
Status: UNOFFICIAL
Build By: @SonicBSV
▪️ Download
▪️ Changelogs
▪️ Notes
▪️ Credits
▪️ Support
Follow @ASUSMaxProM2
Join @ZenfoneMaxProM2Official
#crDroidAndroid #DYNPARTS #X01BD #U #Unofficial #NonFBE
Device: Asus Zenfone Max Pro M2
Codename: X01BD
Build Date: 14-01-2024
Status: UNOFFICIAL
Build By: @SonicBSV
▪️ Download
▪️ Changelogs
▪️ Notes
▪️ Credits
▪️ Support
Follow @ASUSMaxProM2
Join @ZenfoneMaxProM2Official
#crDroidAndroid #DYNPARTS #X01BD #U #Unofficial #NonFBE
🔥16👍10❤4🎉1