[ROM][UNOFFICIAL][10.0] LineageOS 17.1 for UMIDIGI F1 and F1 PLAY

[ROM][UNOFFICIAL][10.0] LineageOS 17.1 for UMIDIGI F1 and F1 PLAY - Miscellaneous Android Development

{
"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"
}

Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Not Working
VoLTE (and will not be fixed due to MTK's proprietary extensions)
Selinux is permissive
FM Radio is Working But No Sound
Sudden Shutdown
Instructions :
Flash your phone with the latest stock rom version (20190903 download link )
Boot your F1 Play to the official OS.
Go to `Settings > About phone`, tap `build number` several times to enable developer settings.
Go to `Settings > System > Developer Settings`, enable `OEM unlocking` and `ADB debugging`.
Connect your phone to your PC and open a terminal or a command line window.
Run `adb reboot bootloader` on your PC (there is no way to enter bootloader directly, only possible through adb).
Run `fastboot flashing unlock` and comfirm unlock on device (THIS WILL WIPE ALL DATA!).
Run `fastboot reboot` to reboot your device and now you should see an unlocked warning during boot screen with orange state.
Download the latest build and gapps
Power off
Press on Power+Volume up button to boot up to Fastboot
Execute "fastboot flash recovery TWRP 3.X.X_F1(or Play).img"
Wait to Finish And Execute "fastboot reboot recovery"
Wipe Data,System,Cache
Flash the latest build
Flash gapps(optional)
Flash Magisk(optional)
Reboot
Downloads :
F1 : https://www.mediafire.com/file/ff5pab2m47wm20g/lineage-17.1-20220515-UNOFFICIAL-F1.zip/file
F1 Play : https://www.mediafire.com/file/d5e8apmil5qpeo7/lineage-17.1-20220515-UNOFFICIAL-F1_EEA.zip/file
Gapps : https://opengapps.org/
TWRP 3.6.1 Recovery for F1 Play : https://www.mediafire.com/file/dn8mzk8bpulvqig/TWRP_3.6.1-F1_Play.img/file
TWRP 3.6.1 Recovery for F1 : https://www.mediafire.com/file/91k98oii8ab7j1l/TWRP_3.6.1-F1.img/file
TWRP 3.3.1 Recovery for F1 Play : https://www.mediafire.com/file/okky2dmgd5zupql/TWRP-3.3.1-F1_Play.img/file
TWRP 3.3.1 Recovery for F1 : https://www.mediafire.com/file/ei83p1lwjupavdd/TWRP-3.3.1-F1.img/file
PBRP Recovery F1 Play : https://www.mediafire.com/file/sl2t7vdqy1ztfsi/PBRP-3.1.0-F1_Play.img/file
PBRP Recovery F1 : https://www.mediafire.com/file/1omqnnh0bvnbath/PBRP-3.1.0-F1.img/file
Magisk : https://github.com/topjohnwu/Magisk/releases/download/v24.3/Magisk-v24.3.apk
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Changelog:
- 07-02-2021 : Initial build
- 20-03-2021 :
*Fix display Lags
*Added Material Files and GoCamera
*Fix GoCamera Video Recording bug
*Added F1 Build
*Fix 'dev/fm' Permission Error
*Fix Incoming Call Bug
- 24-04-2021 :
*Fix Incoming call bug (now really fixed)
*Add LiveDisplay (but it not working cause of kernel)
*Back to LineageOS Charge Animation
*Fix Some Carriers does not Work
*Fix "Stuck at SIM Card Pin"
*Fix Random Reboot and recovery loop (I Think because of TWRP if you have this issue flash LineageOS Recovery)
*Add Face Unlock
*Add DT2W (double tap to wake)
*Fix Write Access to System partition (you need to flash LineageOS Recovery)
- 3-06-2021 :
Build TWRP 3.5.2 For both devices from scratch
- 17-07-2021 :
* Fix in call bug in F1 and F1 play (my mistake)
* Update some system Apps
* For NOW use TWRP 3.3.1 Cause it Works well with Data Encryption
- 28-07-2021 :
* Fix Recovery Loop on TWRP 3.3.1 on F1 and F1 Play (flash the newest recovery to fix recovery loop)
* For NOW use TWRP 3.3.1 Cause it Work well with Data Encryption
- 06-08-2021 :
- Fix FM Radio (finally)
- Add Chromuim instead of jelly
- Fix Video Encoding on Chromuim Based Browsers
- Disable LiveDisplay (not entirely there is in settings)
- Revert back to Snap ( LineageOS Camera) instead of Google Camera Go (to fix video recording issue)
- 10-08-2021 :
- Revert Back to Jelly Browser (Chromuim has some issues)
- Fix Sound Distortion via Besloudness Settings APP (you can still enable/disable Besloudness audio Feature)
- Use LineageOS NFC Stacks instead of Prebuilted One from Vendor (fix Random shutdown)
- 19-08-2021 :
- add support AOD (Always on Display)
- Remove LiveDisplay(now is removed from settings)
- add support Night Light and fix the flicker when enabled
- Add MiraVision(not working for now)
- Improve System Stability and performance
- Enable insecure ADB for debugging
21-8-2021 :
- Fix Besloudness Settings not found
- Fix low brightness is still not low
- Drop MiraVision Support(need a lot of mediatek properties that are closed source code)
25-4-2022 :
- April security updates included
- Add Treble gsi Patches for more stability
- release with TWRP 3.6.1 and PBRP 3.1.0
1-5-2022 :
- Hide DocumentsUI Icon (cause we have a file manager)
- Drop and disable LiveDisplay
- Revert and Enable Night Light (Work Well)
- fix playing video on Chrome will reboot the phone
- some other improvements i forgot
15-5-2022 :
- Fix an error in system property
- Use a bigger APN config to fix "service is unavailable"
- Update Material Files
Click to expand...
Click to collapse
For Donations:
Feel free to donate to support this project.
Credits:
UMIDIGI
PeterCxy [for his device tree for f1]
a-dead-trousers[For some code from his device tree]
XDAevDB Information
LineageOS 17.1 for UMIDIGI F1 and F1 Play, ROM for Miscellaneous Android Development
Contributors
Shadow Of Leaf
Source Code: https://github.com/Shadowofleaf/android_device_umidgi_f1_play
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: LineageOS
Version Information
Status: Beta
Created 2021-02-07
Last Updated 2022-05-15

Hey there, i do have a problem with setting up the rom. Wifi doesn't work for me. While in the google setup it doesn't show any networks and doesn't show my ip/mac below. When i skip the setup and try to activate wifi in the settings, it always intantly turns it off again.
LineageOS version:
17.1 20210205 Build
LineageOS Download url: https://www.mediafire.com/file/4flx8655kchinrt/lineage-17.1-20210205-UNOFFICIAL-F1_Play.zip/file
Gapps version:
ARM64 10.0 Pico 20210206 Build
wipe:
Coming from stock MT6771_20190515, did a full wipe (System/Data/Cache/Dalvik) and flashed above versions. No errors while flashing/booting.
restore with titanium backup:
/
reboot after having the issue:
No reboots/bootloops
No Modifications. Going back to stock Wifi works again.
Tried dirty flashing the rom a second time after the first boot up. Also tired flashing with/without Magisk 21.4.
i don't know how to get logs or if they would even be of importance here, if so let me know and i'll search up how to get them.

IvI97 said:
Hey there, i do have a problem with setting up the rom. Wifi doesn't work for me. While in the google setup it doesn't show any networks and doesn't show my ip/mac below. When i skip the setup and try to activate wifi in the settings, it always intantly turns it off again.
LineageOS version:
17.1 20210205 Build
LineageOS Download url: https://www.mediafire.com/file/4flx8655kchinrt/lineage-17.1-20210205-UNOFFICIAL-F1_Play.zip/file
Gapps version:
ARM64 10.0 Pico 20210206 Build
wipe:
Coming from stock MT6771_20190515, did a full wipe (System/Data/Cache/Dalvik) and flashed above versions. No errors while flashing/booting.
restore with titanium backup:
/
reboot after having the issue:
No reboots/bootloops
No Modifications. Going back to stock Wifi works again.
Tried dirty flashing the rom a second time after the first boot up. Also tired flashing with/without Magisk 21.4.
i don't know how to get logs or if they would even be of importance here, if so let me know and i'll search up how to get them.
Click to expand...
Click to collapse
the fact that wifi is not working is the vendor is old
try the latest stock rom 20190903
https://community.umidigi.com/forum.php?mod=viewthread&tid=18875&extra=page%3D1
flash it with sp flash tool and test again lineageos

new build for f1 play with fixed bugs and a lot of improvements
f1 build soon enough stay tune

Shadow Of Leaf said:
new build for f1 play with fixed bugs and a lot of improvements
f1 build soon enough stay tune
Click to expand...
Click to collapse
That's great!
Will be waiting for the next F1 (non play) next update here. I will flash it and let you know how it goes. Hopefully network signal is not extremely low as GSIs.

soulfisher7 said:
That's great!
Will be waiting for the next F1 (non play) next update here. I will flash it and let you know how it goes. Hopefully network signal is not extremely low as GSIs.
Click to expand...
Click to collapse
really soon i will upload it
stay tune

soulfisher7 said:
That's great!
Will be waiting for the next F1 (non play) next update here. I will flash it and let you know how it goes. Hopefully network signal is not extremely low as GSIs.
Click to expand...
Click to collapse
i upload the latest build for f1
try it out to see if you have that signal problem

Shadow Of Leaf said:
i upload the latest build for f1
try it out to see if you have that signal problem
Click to expand...
Click to collapse
Thanks for the quick upload.
- F1, latest international stock build, rooted.
- Removed root, flashed stock boot.img
- wiped system, data, cache, dalvik
- Flashed F1 LOS build: 17.1 - 20210424
- gapps: open_gapps-arm64-10.0-nano-20210424
- magisk: v21.4
- apps restored via swift backup
Issues: will update when/if I notice any.
Once again thank you for the ROM, much appreciated.

- Network signal is unreliable, similar to the GSI behavior. I am on the international stock version, and I assume it uses the same vendor image as the European. Is there a difference?
- Double tap to wake does not work.
- ram management is better than stock, but it's not as good as other GSIs, which is odd for LOS.

soulfisher7 said:
- Network signal is unreliable, similar to the GSI behavior. I am on the international stock version, and I assume it uses the same vendor image as the European. Is there a difference?
- Double tap to wake does not work.
- ram management is better than stock, but it's not as good as other GSIs, which is odd for LOS.
Click to expand...
Click to collapse
it work but not all the time and it related to kernel (is prebuilted)
for ram management i see what i can do

new TWRP 3.5.2 Build for UMIDIGI F1 and F1 Play
Test it out for bugs and for decryption if it work

Hi, use Umidigi F1 Play and rom link: https://www.mediafire.com/file/n85cz0oyei5qvlv/lineage-17.1-20210416-UNOFFICIAL-F1_Play.zip/file
Gapps Version: open_gapps-arm64-10.0-pico-20210605
Still No Call Issue Continue and com.tek.ims.Application stopping error on installation screen. Please fix this problem. I don't want to return stock rom.
(I don't know English well, sorry if I said something wrong)

Crhada17 said:
Hi, use Umidigi F1 Play and rom link: https://www.mediafire.com/file/n85cz0oyei5qvlv/lineage-17.1-20210416-UNOFFICIAL-F1_Play.zip/file
Gapps Version: open_gapps-arm64-10.0-pico-20210605
Still No Call Issue Continue and com.tek.ims.Application stopping error on installation screen. Please fix this problem. I don't want to return stock rom.
(I don't know English well, sorry if I said something wrong)
Click to expand...
Click to collapse
carrier network is shown at full ?
and i will look into this ims problem
thanks for the report
and did you found any bug related to new TWRP 3.5.2

O
Shadow Of Leaf said:
carrier network is shown at full ?
and i will look into this ims problem
thanks for the report
and did you found any bug related to new TWRP 3.5.2
Click to expand...
Click to collapse
carrier network is shown at full ?
yes, there is no problem of not seeing the line connected to the operator network.
I can call others, but they cannot call me, the
person you are calling is not reachable.
did you found any bug related to new TWRP 3.5.2
I didn't see any problem, but it doesn't backup. I think this error appears because the device is encrypted.

Crhada17 said:
Hi, use Umidigi F1 Play and rom link: https://www.mediafire.com/file/n85cz0oyei5qvlv/lineage-17.1-20210416-UNOFFICIAL-F1_Play.zip/file
Gapps Version: open_gapps-arm64-10.0-pico-20210605
Still No Call Issue Continue and com.tek.ims.Application stopping error on installation screen. Please fix this problem. I don't want to return stock rom.
(I don't know English well, sorry if I said something wrong)
Click to expand...
Click to collapse
carrier network is shown at full ?
and i will look into this ims problem
thanks for the report
and did you found any bug related to new TWRP
Crhada17 said:
O
carrier network is shown at full ?
yes, there is no problem of not seeing the line connected to the operator network.
I can call others, but they cannot call me, the
person you are calling is not reachable.
did you found any bug related to new TWRP 3.5.2
I didn't see any problem, but it doesn't backup. I think this error appears because the device is encrypted.
Click to expand...
Click to collapse
thanks for report out
the call issue is my fault i forgot to use my fixed mtk-ril.so instead of the faulty one in vendor
for the com.tek.ims force application is just force closed the first time booting in lineageos is not big deal
i will fix the call issue and fm radio and build new one so stay tune
i think the big problem is the decryption in twrp i need to fix it

Shadow Of Leaf said:
carrier network is shown at full ?
and i will look into this ims problem
thanks for the report
and did you found any bug related to new TWRP
thanks for report out
the call issue is my fault i forgot to use my fixed mtk-ril.so instead of the faulty one in vendor
for the com.tek.ims force application is just force closed the first time booting in lineageos is not big deal
i will fix the call issue and fm radio and build new one so stay tune
i think the big problem is the decryption in twrp i need to fix it
Click to expand...
Click to collapse
Shadow Of Leaf said:
carrier network is shown at full ?
and i will look into this ims problem
thanks for the report
and did you found any bug related to new TWRP
thanks for report out
the call issue is my fault i forgot to use my fixed mtk-ril.so instead of the faulty one in vendor
for the com.tek.ims force application is just force closed the first time booting in lineageos is not big deal
i will fix the call issue and fm radio and build new one so stay tune
i think the big problem is the decryption in twrp i need to fix it
Click to expand...
Click to collapse
Good luck bro

Crhada17 said:
Good luck bro
Click to expand...
Click to collapse
thanks

Shadow Of Leaf said:
carrier network is shown at full ?
and i will look into this ims problem
thanks for the report
and did you found any bug related to new TWRP
thanks for report out
the call issue is my fault i forgot to use my fixed mtk-ril.so instead of the faulty one in vendor
for the com.tek.ims force application is just force closed the first time booting in lineageos is not big deal
i will fix the call issue and fm radio and build new one so stay tune
i think the big problem is the decryption in twrp i need to fix it
Click to expand...
Click to collapse
bro when will you post the fixed version?
If other problems will take a long time, you can at least post a fixed version of the problem of not receiving calls.

Shadow Of Leaf said:
the call issue is my fault i forgot to use my fixed mtk-ril.so instead of the faulty one in vendor
for the com.tek.ims force application is just force closed the first time booting in lineageos is not big deal
i will fix the call issue and fm radio and build new one so stay tune
i think the big problem is the decryption in twrp i need to fix it
Click to expand...
Click to collapse
I've been waiting for a long time, any progress

Shadow Of Leaf said:
carrier network is shown at full ?
and i will look into this ims problem
thanks for the report
and did you found any bug related to new TWRP
thanks for report out
the call issue is my fault i forgot to use my fixed mtk-ril.so instead of the faulty one in vendor
for the com.tek.ims force application is just force closed the first time booting in lineageos is not big deal
i will fix the call issue and fm radio and build new one so stay tune
i think the big problem is the decryption in twrp i need to fix it
Click to expand...
Click to collapse
sorry bro i bothered you a bit but it's a really good rom but i can't use it because of incoming call problem can you spare some of your precious time
thank you

Related

[ROM][Official][Weekly] LineageOS 14.1 for OnePlus 3/3T

LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Important information:
This thread is for official LineageOS 14.1 builds for OnePlus 3/3T. The following will not be supported here:
Custom kernels
Mods
Xposed
We don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Known bugs:
Front camera is buggy, due to the buggy camera HAL Fixed by OnePlus
Installation:
First time flashing LineageOS 14.1 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery (See #2 for details)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon package, install the SU addon package(https://download.lineageos.org/extras, choose arm64)
Reboot
Source code:
https://github.com/lineageos
Credits:
LineageOS Team & Contributors
Code Aurora Forum
......
Download:
https://download.lineageos.org/oneplus3
XDA:DevDB Information
LineageOS, ROM for the OnePlus 3
Contributors
dianlujitao, Grarak
Source Code: https://github.com/lineageos
ROM OS Version: 7.x Nougat
Version Information
Status: Nightly
Created 2016-11-09
Last Updated 2017-03-27

Release note:
New builds (after 2017/1/15) uses F2FS backported from 4.10 kernel, you may meet compatibility problems such as deadlocks, if you do, flash TWRP provided in OP and choose "Wipe -> Format Data" to format(not just wipe) your /data partition, this will clean the entire /data partition, including the emulated sdcard, so don't forget to backup your data before. After that, your data partition will be formatted into ext4, if you want to keep using f2fs, just convert fs type normally in TWRP.
[*]For oneplus3, my unofficial TWRP is recommended, as it's what I use. For 3T, TWRP 3.0.4 is recommended.
As of 2017/6/17, official TWRP for OnePlus 3(https://dl.twrp.me/oneplus3/) is updated with latest LineageOS kernel and OxygenOS decryption stuff, it builds against Omni 7.1.2 and supports both op3&3t, now it's the recommended recovery.
20170120 build includes sdcardfs, security fixes and camera fixes&improvements, touch to focus is fixed as well, if it's still not working, clean Snap's data. BTW N kernel source is released now, I'll take days to bring up, don't ask for ETA.
Regarding installation, we recommend that users wipe when switching to LineageOS, and reinstall their gapps. However, we recognize that this can be time consuming, so we are offering an EXPERIMENTAL (read as, if it fails, you’ll have to wipe anyways) solution. Visit http://lineageos.org/Update-and-Build-Prep/for more details
Started from lineage-14.1-20170207-nightly-oneplus3-signed.zip, we provide unified builds for both 3&3T, and you need to install certain firmware to pass the TrustZone assertion. Currently they're the OxygenOS Open Beta 19/11 ones. As oneplus won't update them every time new OTAs are rolling out, firmware from other versions might also pass the assertion.
FAQs:
My status bar quick pulldown and notification slider are broken, why?
See https://github.com/opengapps/opengapps/wiki/Notes-for-CMSetupWizard
Why the builds are unified?
Tell me the difference between OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883 and OnePlus3TOxygen_28_OTA_039_all_1701140132_de9036f11e2246a8, why not?
{
"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"
}

Latest Firmware files for oneplus3/oneplus3t -5.7.2017-
Make a nandroid backup before you proceed
Flash the following files using the latest official twrp to avoid any recovery related issues.
Make sure to do a clean flash if your rom requires an updated firmware.
Don't ever flash an oneplus3 firmware on oneplus3t or an oneplus3t firmware on oneplus3.
Oneplus3
Instructions only for oneplus3!
1-clean flash is recommended.
2-Falsh OnePlus3_OpenBeta19-FIRMWARE+MODEM-flashable.zip.
3-Flash the latest laos nightly.
4-optional: gapps arm64 7.1 and -su-addon arm64, this enables inbuild laos root.
5-Wipe Dalvik/cache and reboot.
Oneplus3t
Instructions only for oneplus3t!
1-clean flash is recommended.
2-Flash OnePlus3T_Beta10-(4-7-17)-FIRMWARE-flashable.zip.
3-Flash the latest laos nightly
4-optional: gapps arm64 7.1 and -su-addon arm64, this enables inbuild laos root.
5-Wipe Dalvik/cache and reboot.
For people who rather use the oxygenos camera:
Get OnePlusCameraV8-siankatabg.apk and OnePlusGallery-V8-siankatabg.apk
If you have problems after flashing any custom kernels please provide a log in the thread where you got the kernel from and not here!
Credits:
@nvertigo67 @djsubterrain @Eliminater @kamilmirza op3t firmware
@jamal2367 op3 firmware
@siankatabg oos camera/gallery port

Maybe let a CM member start the official thread?

@dianlujitao : Thanks for maintaining this.
Currently call audio is broken by sound trigger commit.
Even when that revert, noise cancellation not working / echo happens while in calls.
please fix this only issue.

RohanAJoshi said:
@dianlujitao : Thanks for maintaining this.
Currently call audio is broken by sound trigger commit.
Even when that revert, noise cancellation not working / echo happens while in calls.
please fix this only issue.
Click to expand...
Click to collapse
Steve is investigating on that

dianlujitao said:
Steve is investigating on that
Click to expand...
Click to collapse
That's great, waiting for noise cancellation fix.

I have a custom TWRP from the OOS 3.5.5 (OnePlus thread),
twrp-3.0.2-22-oneplus3.img
I think only that is working correctly with CM 14.1 Official ROM ?

osr.arora said:
I have a custom TWRP from the OOS 3.5.5 (OnePlus thread),
twrp-3.0.2-22-oneplus3.img
I think only that is working correctly with CM 14.1 Official ROM ?
Click to expand...
Click to collapse
Yes, 3.0.2.19 & 3.0.2.22 should work with every rom.
So use always this twrp versions to get sure.
dianlujitao said:
Steve is investigating on that
Click to expand...
Click to collapse
Finally someone official is here
Thank you very much!!!
Can you just tell me,
Is that included baseband/firmware inside the rom, 3.5.5 or 3.2.7 or mixed or sth else?
Thanks
Cheers

Is possible flash 14.1nightly on experimental? I have from 2 weeks

alteus83 said:
Is possible flash 14.1nightly on experimental? I have from 2 weeks
Click to expand...
Click to collapse
It is possible, but you can get some unexpected bugs...
Better to do a clean start, with full wipe.
And dirty flash upcoming nightlys.
Cheers

When i plug my Phone into the charger or my pc the charging icon wont show up (lighting bolt in the battery)
After install i tried a cache/dalvik clear, did not help
The Phone is connected to the computer, it says charging..
https://postimg.org/image/xj8af43tf/

yooouuri said:
When i plug my Phone into the charger or my pc the charging icon wont show up (lighting bolt in the battery)
After install i tried a cache/dalvik clear, did not help
The Phone is connected to the computer, it says charging..
https://postimg.org/image/xj8af43tf/
Click to expand...
Click to collapse
known issue with cm14.1

yooouuri said:
When i plug my Phone into the charger or my pc the charging icon wont show up (lighting bolt in the battery)
After install i tried a cache/dalvik clear, did not help
The Phone is connected to the computer, it says charging..
https://postimg.org/image/xj8af43tf/
Click to expand...
Click to collapse
This is known... There are some problems with battery icon and battery stats too...
@dianlujitao
OP need to add that bugs into to the bug list:
1. Echo (loudspeaker) noise calcellation
2. Battery stats reset + charging text + charging icon
3. GPS problems especially while driving. (you get a perfect gps fix but if you move fast "drive" you get wrong coordinates)
4. All bugs related to legacy HAL1
5. Srgb colors not working
Cheers

Ramalama said:
This is known... There are some problems with battery icon and battery stats too...
OP need to add that bugs into to the bug list:
1. Echo (loudspeaker) noise calcellation
2. Battery stats reset + charging text + charging icon
3. GPS problems especially while driving. (you get a perfect gps fix but if you move fast "drive" you get wrong coordinates)
4. All bugs related to legacy HAL1
Cheers
Click to expand...
Click to collapse
Agree! :good:

Ramalama said:
This is known... There are some problems with battery icon and battery stats too...
@dianlujitao
OP need to add that bugs into to the bug list:
1. Echo (loudspeaker) noise calcellation
2. Battery stats reset + charging text + charging icon
3. GPS problems especially while driving. (you get a perfect gps fix but if you move fast "drive" you get wrong coordinates)
4. All bugs related to legacy HAL1
Cheers
Click to expand...
Click to collapse
You guys may need to wait because cm14.1 is still highly experimental

So its waiting for OP to release some of their HAL?

Ramalama said:
This is known... There are some problems with battery icon and battery stats too...
@dianlujitao
OP need to add that bugs into to the bug list:
1. Echo (loudspeaker) noise calcellation
2. Battery stats reset + charging text + charging icon
3. GPS problems especially while driving. (you get a perfect gps fix but if you move fast "drive" you get wrong coordinates)
4. All bugs related to legacy HAL1
Cheers
Click to expand...
Click to collapse
Add on
5. In call volume slider not working in speaker or headset mode.

dianlujitao said:
You guys may need to wait because cm14.1 is still highly experimental
Click to expand...
Click to collapse
You have right, but that's the actual bug list that users know what's not working atm
I don't think that next few builds will not be highly experimental
yooouuri said:
So its waiting for OP to release some of their HAL?
Click to expand...
Click to collapse
Yes, till they release nougat.
mgear356 said:
Add on
5. In call volume slider not working in speaker or headset mode.
Click to expand...
Click to collapse
I know, but this bug is only since yesterday, there is a commit that broke it... I think it will be fixed on next 1-2 builds...
Cheers

I would appreciate if op could add link to supported twrp in the first post.. It would be really helpful..

[ROM] [ 8.0.0 ] Official madOS - Oukitel K6000 Plus [MT6750]

{
"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"
}
This is a Official Build of madOS ( based on AOSP Oreo ) for Oukitel K6000 Plus with MTK 6750 SoC
madOS is based on pure A.O.S.P. with many additional customizations and MediaTek support.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Installation Instructions:
Download ROM from M.A.D. Facebook
OR from xda DevDB
Download OpenGapps nano or pico from OpenGapps
(choose Arm64 and Android 8.0 )
Backup
Unlock Bootloader Bootloader unlock
Flash new mandatory new Oreo TWRP (available on downloads)
Boot to the new TWRP recovery
full Wipes (dont come crying if you didn't .. ;p )
Install rom (optionally following by GAPPS if you use them)
Optional: go to: wipe --> Advanced Wipe, tick 'cache' and klick 'repair or change File System' --> change File System --> F2FS --> swipe to the right (hit back several times, and proceed the same way with 'data').
Reboot System
Working:
RIL (Calls /SMS, Data connection, etc)
Wifi
Bluetooth
FM Radio
All Sensors (including fingerprint)
Lights; HW Keys
Both storages & MTP
HW de/encoding
Camera (photos and video)
GPS & aGPS
Audio
madOS Extras (the features ya'all used too), plus, some new features we added on Oreo)
Not working:
nothing known
XDA:DevDB Information
madOS_O_K6KP, ROM for all devices (see above for details)
Contributors
DerTeufel1980, superdragonpt, fire855
Source Code: https://github.com/MediatekAndroidDevelopers
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: bootloader unlocked, twrp
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2017-11-19
Created 2017-11-19
Last Updated 2017-12-31

Reserved
How-To unlock Bootloader and install TWRP
ATTENTION: This is voiding your warrenty
Install minimal adb and fastboo to your PCt: Minimal ADB and Fastboot
On the smartphone: Go to Settings --> About Phone and hit 'build Number' seven times, to enable 'Developer Options'
Go to Settings --> Developer Options, and allow usb-debugging and allow OEM-unlocking (For bootloader unlock)
Connect the smartphone to the pc. On the smartphone accepts the adb connection with the pc
Start 'Minimal adb and Fastboot' at Pc. In the command window, type: "adb reboot bootloader" and press Enter (this is restarting the smartphone into the bootloader)
WARNING: This step deletes all data from the smartphone, returns it to the factory setting and leads to the loss of the warranty! In the command window, type "fastboot oem unlock" and press Enter (to unlock the bootloader). You probably need to press some button of the phone to confirm (check the display for this)
Download the Twrp image: Oukitel K6000 Plus TWRP, and copy the recovery.img file to the installation folder of 'minimal adb and fastboot'
In the command window, type "fastboot flash recovery recovery.img" and press Enter. After successful flash, enter "fastboot reboot" in the command window, press 'Enter'. Then immediately press and hold 'volume up key' on the smartphone (Until a small menu appears)
3 options appear on the smartphone: Recovery, Fastboot, Normal. You can navigate with 'volume up key' and confirm your selection with 'volume down'. Navigate to Recovery and press the volume down key to confirm (Smartphone starts now the Installed TWRP Recovery)

F.A.Q
General F.A.Q.
Q: What the hell is madOS ?
A: madOS, (M.A.D. Team OS), is a ROM based on pure A.O.S.P. with extended capabilities and customizations made by or merge/adapted by M.A.D. Team.
Q: Where to report bugs ?
A: madOS issue tracker
Q: Which recovery should I use for this ROM?
A: Latest M.A.D. TWRP recovery
--> Download Section
Q: How do i flash a new recovery or new boot from previous TWRP?
A:
1: You can flash it with a scatter file
2: You can simply flash it from the existing twrp recovery: Install> Install image> Select RECOVERY or BOOT image file > Select "Recovery" or "Boot" as partition to flash.
Reboot
Q: Do i need to make full wipes?
A: YES, dont come crying at me, if you didn't .... ;p
Q: What is "full wipes" ?
A: To Wipe : Cache; System; DATA ...
Q: What should i use f2fs or ext4?
A: Both are supported, choose the one you desire, where f2fs might be faster
Q: is the Data connection issue of going to / from 4G present?
A: nope data switchs pretty fast on our new RIL
2G>3G>4G | 4G>3G>2G pretty fast
Q: Does this rom have any Theme support
A: Yup, We have working Theme Engine (madOS extras)
Q: Some translations are missing for my language, can I help?
A: Sure you can, please check our translations repo available here , you can either do a pull request, or if you don't know how to work with git, sent us the XML. Strings for your language ( Check Readme on repo).
Q: What's working ?
A: Check first Post for current status
Q: App "x" doesn't work, why?
A: Probably not compatible with OREO yet, feedback is welcome
Q: Is the rom rooted?
A: NO, But you can easily root with Magisk v14 onwards.
Q: Does xposed work?
A: Is there Xposed for O? ... then no ;p
Q: How is battery life with Oreo?
A: Pretty awesome
Q: Does this build support Vulcan?
A: No....duh! v
Q: Does doze work in this build?
A: Yup
Q: when will (feature/issue here) be fixed?
A: NO ETA , please
Porting F.A.Q.
No porting support, no port questions allowed on this thread, and porting PMs will be auto-deleted, porting replies will be reported as well
G.APPS F.A.Q.
Q:What GAPPS package should I use?
A: OpenGapps arm64 nano/mini
Q: How to properly install GAPPS?
A:Flash Rom + Flash Gapps at once
CREDITS and Thanks
madOS Team
Our translators, credits list here
A.O.S.P.
Pure Nexus
AOSPA
DU (Dirty Unicorns)
Omni
HELP supporting madOS
We do this on our free time, however we do have costs on maintaining this :/
Any donation is highly appreciated
You can donate by using
this link
If the above doesn't work in your country, then you can directly donate by using this e-mail adress: [email protected]
About madOS Proprietary Apps
You are NOT allowed by any means, to use our madOS apps on any other build, your rom
This is exclusively for OFFICIAL madOS ROM releases
@To Moderators: Feel free to clean the thread, whenever users start spamming, severe OT, or questioning about porting...

Changelogs
[Stable] Build [8.0.0] 20171119
First Release
Patch Level: 8.0.0 [OPR1] November 6, 2017
Kernel: 3.18.80( Oreo branch)

one more
reserved

DerTeufel1980 said:
Changelogs
[Stable] Build [8.0.0] 20171119
First Release
Patch Level: 8.0.0 [OPR1] November 6, 2017
Kernel: 3.18.80( Oreo branch)
Click to expand...
Click to collapse
Hi guys,
Thanks for your incredible work for the K6000 Plus!
I have a Doogee Y6. It uses the same kernel as K6000 plus. So, I've been trying to compile the k6000 plus kernel in order to work on my phone (I have made the necessary adjustments regarding my device's specific drivers such as LCM, Touchscreen, fingerprint etc.)
But I am running into errors. The compiler complains about not finding some files like: mt_gpufreq.h, cmdq_engine.h etc.
Can you assist me with this?
Thank you.

Great ROM! Many thanks for your work M.A.D team
I found one bug in camera. When you turn on HDR mode and after taking picture camera force close with toast: "Media server died, closing camera." but photo still save so not big deal
--- edit ---
More bugs:
1. I can't change cpu governor
2. WiFi icon and battery icon in statusbar are always black: - bug gone after restart
3. Phone freeze sometimes for a sec.

Eselter said:
Great ROM! Many thanks for your work M.A.D team
I found one bug in camera. When you turn on HDR mode and after taking picture camera force close with toast: "Media server died, closing camera." but photo still save so not big deal
--- edit ---
More bugs:
1. I can't change cpu governor
2. WiFi icon and battery icon in statusbar are always black: - bug gone after restart
View attachment 4337841
3. Phone freeze sometimes for a sec.
Click to expand...
Click to collapse
Thx for your feedback. I'll take a look.... Changing CPU governors is more than less just a left over from older phones... We may just remove this option. There aren't actually useful governors to switch to.
In which situations did it freeze?
Sent from my uhans h5000, running Android 8.0.0

I dont know why, but when i trying to boot in new TWRP recovery, the phone's screen just glows gray.
Can u help me with this? Firmware v23, bootloader unlocked. What's wrong?

DerTeufel1980 said:
Thx for your feedback. I'll take a look.... Changing CPU governors is more than less just a left over from older phones... We may just remove this option. There aren't actually useful governors to switch to.
In which situations did it freeze?
Sent from my uhans h5000, running Android 8.0.0
Click to expand...
Click to collapse
Most often while scrolling (ex in app drawer or browser) and click on some button (ex keyboard). I think it can be releated to CPU hotplug.

xasdfx_ said:
I dont know why, but when i trying to boot in new TWRP recovery, the phone's screen just glows gray.
Can u help me with this? Firmware v23, bootloader unlocked. What's wrong?
Click to expand...
Click to collapse
You flashed the recovery from the download section, right?
Does it show the twrp logo in the beginning?
Eselter said:
Most often while scrolling (ex in app drawer or browser) and click on some button (ex keyboard). I think it can be releated to CPU hotplug.
Click to expand...
Click to collapse
OK. I'll try to reproduce it
Sent from my uhans h5000, running Android 8.0.0

And one more minor bug. In quick settings on weather tile button more settings don't work. If someone wonder it can be adjusted in madOS extras.

DerTeufel1980 said:
You flashed the recovery from the download section, right?
Does it show the twrp logo in the beginning?
Click to expand...
Click to collapse
Yes, of course.
Nope., it doesnt show anything. Oukitel logo - gray sreen. I changed the display on my phone(the old one cracked), maybe the reason is this?

Next two minor bugs:
1. Changing implementation of webview don't work. Phone always using chromium engine.
2. Normal reboot freeze phone. Soft and reboot to recovery works fine.
BTW: do you have some bug tracker ?
And one more:
Battery capacity are wrongly reported.

xasdfx_ said:
Yes, of course.
Nope., it doesnt show anything. Oukitel logo - gray sreen. I changed the display on my phone(the old one cracked), maybe the reason is this?
Click to expand...
Click to collapse
****... Unfortunately I have no idea how to fix it then... We can only use the drivers shared by oukitel. If there's something missing, we're out of luck...
Eselter said:
Next two minor bugs:
1. Changing implementation of webview don't work. Phone always using chromium engine.
2. Normal reboot freeze phone. Soft and reboot to recovery works fine.
BTW: do you have some bug tracker ?
And one more:
Battery capacity are wrongly reported.
Click to expand...
Click to collapse
Webview implementation... We'll check as well, but that's not very important.
Does it always freeze? And where/when? During the new boot, or before shutting down?
In which situations/apps is the battery capacity reported wrong?
Sent from my uhans h5000, running Android 8.0.0

DerTeufel1980 said:
Does it always freeze? And where/when? During the new boot, or before shutting down?
Click to expand...
Click to collapse
Until now always (I try more than 10 times) before shutting down on message rebooting, but now is working fine (magic ;>).
DerTeufel1980 said:
In which situations/apps is the battery capacity reported wrong?
Click to expand...
Click to collapse
In apps: CPU Info and AccuBattery. I don't know if this have impact on battery status in system?

And one glitch very paintful for me :/
Android Auto has problem with displaying on car screen (and Android Studio):
View attachment 4338823

Eselter said:
And one glitch very paintful for me :/
Android Auto has problem with displaying on car screen (and Android Studio):
View attachment 4338823
Click to expand...
Click to collapse
I'll try to check this. We unfortunately don't own a car which supports this
Sent from my uhans h5000, running Android 8.0.0

https://developer.android.com/training/auto/testing/index.html
@DerTeufel1980 my screenshot was made from above tool for devs but in car it look exactly the same
So you can use it to reproduce and debug the glitch.

One more thing related to car. Calls via car speakers not working. Music, call log, contacts working fine via Bluetooth but calls always switch to phone speakers/microphone.

[ROM] [ 8.1.0 ] Official madOS - Vernee Apollo Lite & X [MT6797]

{
"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"
}
This is a Official Build of madOS ( based on AOSP 8.1.0 ) for Vernee Apollo Lite & X with MTK 6797 SoC
madOS is based on pure A.O.S.P. with many additional customizations and MediaTek support.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Installation Instructions:
The latest 7.1.2 build must be flashed in SPFT with firmware upgrade mode before this ROM can be flashed (Downloads: VAL, VAX)
Download ROM from M.A.D. Facebook
OR from xda DevDB
Download 8.1 GApps from xda devdb (Mirror)
Backup
Flash new mandatory new Oreo TWRP (available on downloads)
Boot to the new TWRP recovery
full Wipes (dont come crying if you didn't .. ;p )
Install rom (optionally following by GAPPS if you use them)
Optional: go to: wipe --> Advanced Wipe, tick 'cache' and klick 'repair or change File System' --> change File System --> F2FS --> swipe to the right (hit back several times, and proceed the same way with 'data').
Reboot System
Working:
RIL (Calls /SMS, Data connection, etc)
Wifi
Bluetooth
FM Radio
All Sensors
Fingerprint
Lights
Both storages & MTP
HW de/encoding
Camera (photos and video)
GPS & aGPS
Audio
madOS Extras (the features ya'all used too), plus, some new features we added on Oreo)
Bugs:
-
XDA:DevDB Information
madOS_O_VAL_VAX, ROM for all devices (see above for details)
Contributors
fire855, DerTeufel1980, superdragonpt
Source Code: https://github.com/MediatekAndroidDevelopers
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP
Based On: AOSP
Version Information
Status: Stable
Stable Release Date: 2017-12-25
Created 2017-12-25
Last Updated 2018-01-13

General F.A.Q.
Q: What the hell is madOS ?
A: madOS, (M.A.D. Team OS), is a ROM based on pure A.O.S.P. with extended capabilities and customizations made by or merge/adapted by M.A.D. Team.
Q: Which recovery should I use for this ROM?
A: Latest M.A.D. TWRP 3.2.1-0 recovery
--> Check xda Download Section
Q: How do i flash new recovery ?
A:
1: You can flash it with a scatter file (LP rom layout)
2: You can simply flash it from the existing twrp recovery: Install> Install image> Select Oreo TWRP> Select "Recovery" as partition to flash.
Reboot to recovery to use new one
Q: Do i need to make full wipes?
A: YES, dont come crying at me, if you didn't .... ;p
Q: What is "full wipes" ?
A: To Wipe : Cache; System; DATA ...
Q: What should i use f2fs or ext4?
A: Both are supported, choose the one you desire
Q: is the Data connection issue of going to / from 4G still present?
A: nope data switchs pretty fast on our new RIL
2G>3G>4G | 4G>3G>2G pretty fast
Q: Does this rom have any Theme support
A: Yup, We have working Theme Engine (madOS extras)
Q: Some translations are missing for my language, can I help?
A: Sure you can, please check our translations repo available here , you can either do a pull request, or if you don't know how to work with git, sent us the XML. Strings for your language ( Check Readme on repo).
Q: I want to report a bug(s) do you have an issue tracker?
A: Yeah... madOS issue tracker
Q: What's working ?
A: Check first Post for current status
Q: App "x" doesn't work, why?
A: Probably not compatible with OREO yet, feedback is welcome
Q: Is the rom rooted?
A: NO, But you can easily root with :
1: Magisk ( v14 onwards.)
2: Super SU ( v2.82 onwards)
Q: Should i root together with rom ?
A: Not advised.. mainly the Magisk that gives some weird issues...
Flash ROM and GAPPS (if you use gapps), after first boot get back to recovery and flash your desire rooting method
Q: Does xposed work?
A: Is there Xposed for O? ... then no ;p
Q: How is battery life with Oreo?
A: Pretty awesome
Q: Does this build support Vulkan?
A: No....duh! v
Q: Does doze work in this build?
A: Yup
Q: Does 4k video recording work?
A: Yes, but not every phone supports it. If 4k worked in the stock rom, it will work in madOS too.
Q: when will (feature/issue here) be fixed?
A: NO ETA , please
Porting F.A.Q.
No porting support, no port questions allowed on this thread, and porting PMs will be auto-deleted, porting replies will be reported as well
G.APPS F.A.Q.
Q:What GAPPS package should I use?
A:OpenGapps arm64 nano/mini
Since there's no Official GAPPS for 8.1.0 just yet...
... we had built OpenGapps nano and pico versions
--> Check Download Section
Q: How to properly install GAPPS?
A:Flash Rom + Flash Gapps at once
CREDITS and Thanks
madOS Team
Our translators, credits list here
A.O.S.P.
AOSPA
DU (Dirty Unicorns)
Omni
HELP supporting madOS
We do this on our free time, however we do have costs on maintaining this :/
Any donation is highly appreciated
You can donate by using
this link
If the above doesn't work in your country, then you can directly donate by using this e-mail adress: [email protected]
About madOS Proprietary Apps
You are NOT allowed by any means, to use our madOS apps on any other build, your rom
This is exclusively for OFFICIAL madOS ROM releases
@To Moderators: Feel free to clean the thread, whenever users start spamming, severe OT, or questioning about porting...

Changelogs
[Stable] Build [8.1.0] 20171225
First Release
madOS version: 2.1
Patch Level: 8.1.0 [OPM1] December 5, 2017
Kernel: 3.18.89 (o-8.1.0 branch)
[Stable] Build [8.1.0] 20180102
madOS version: 2.1.1
Fixed UI lags / hangs
Fixed deepsleep
Fixed screen recording
Fixed video playback issues
Updated graphics system
Improved GSM/LTE signal handling
Fixed alarms
Fixed FMRadio
Fixed wallpaper scrolling setting in madLauncher
Fixed 5GHz hotspot issues
Improvements in bluetooth for A2DP
Updated included APNs list
madOS color Engine:
Rebased & many improvements on the engine
Better support on theming Quick Settings
New option to override default Google 8.1 QS theming
New reset button to get back to default 8.1 theming
New MAD mode

Merry Christmas !!

Thanks. Merry Christmas.
The computer died. I will not make the sd card backup.

Marry Xmas to all.

Wow.... Oreo release and directly 8.1 weeeeeeeeeeee!
Didn't expect this before the new year, what a surprise.
Thanx you @fire855
Thank you MAD-team

Hi,
How to install ROM and gapps?
On TWRP or using flash?
Thank you

Should we come from the last 7.1.2 build (which has different partitions from stock)?

I really appreciate the work, but it's somewhat unflashable. New recovery is not stable, it gets stuck sometimes. Also I didn't manage to bring 8.1 to run with Gapps yet.
€: To provide somewhat more information: System crashes when running playstore.
€2: Full wipe made, advanced wipe and wiped every partition. It gets stuck coincidential, there's no proper reason for it, it got stuck once when I flashed MadOS itself, second time it got stuck flashing gapps, so I hope I get it run that night...
€3: Recovery freezes and after 30 seconds (approx) phone reboots.
€4: Nope, I don't get it to work, goddamnit. It freezes almost immediately after I enter my pin.

Help please...
I install new TRWP OREO on old twrp...
when reboot the phone shutoff and does nothing... i cant turn on...

TJFA81 said:
Help please...
I install new TRWP OREO on old twrp...
when reboot the phone shutoff and does nothing... i cant turn on...
Click to expand...
Click to collapse
Hold VOL+ and POWER when rebooting. Then you can choose to boot into TWRP. There you copy the new recovery image and then flash Oreo.

Xorianator said:
Hold VOL+ and POWER when rebooting. Then you can choose to boot into TWRP. There you copy the new recovery image and then flash Oreo.
Click to expand...
Click to collapse
I cant...
When choose recovery the phone freezes. black screen
To install new TWRP OREO its only necessary flash the file recovery.img???

TJFA81 said:
I cant...
When choose recovery the phone freezes. black screen
To install new TWRP OREO its only necessary flash the file recovery.img???
Click to expand...
Click to collapse
Yes, you only have to bring the recovery up again.
What you can also do is: Go back to 7.1 (flash it with SPflashtool) and then do the steps

Xorianator said:
Yes, you only have to bring the recovery up again.
What you can also do is: Go back to 7.1 (flash it with SPflashtool) and then do the steps
Click to expand...
Click to collapse
I cant go to recovery...
Can start the phone but cant go to recovery after flash new recovery file posted on MAD facebook.
I dont have 8.1 because of that, just did the first step anda now cant go to recovery

TJFA81 said:
I cant go to recovery...
Can start the phone but cant go to recovery after flash new recovery file posted on MAD facebook.
I dont have 8.1 because of that, just did the first step anda now cant go to recovery
Click to expand...
Click to collapse
Reflash 7.1 image using SPflashtool, I made a guide for this There you go. Then you can repeat.
Okay so 8.1 is not working at all... I get somewhat a weird failure on screen, the screen "sacks" down (main UI Activity just "fall down", status bar is still up) and then it freezes... Looking forward to get this fixed soon.
€: And the boot time is horrible, before I see a screen it's black for idk 2 Minutes
€3: Nvm lol, actually the phone is now unable to boot in System....
€4: Give it a try with "optional" F2FS File system step, let's see.
€5: Nope, didn't fix a thing. So well, at least I could capture this "sack down" thing:
The red line is where the display ends. As you can see the symbols are still in place. The blue line marks where the activity "sack down" and if this happens (which happens just on coincidence) nothing will happen any further, system's frozen and it reboots afterwards.

TJFA81 said:
Hi,
How to install ROM and gapps?
On TWRP or using flash?
Thank you
Click to expand...
Click to collapse
TWRP

Xorianator said:
Reflash 7.1 image using SPflashtool, I made a guide for this There you go. Then you can repeat.
Okay so 8.1 is not working at all... I get somewhat a weird failure on screen, the screen "sacks" down (main UI Activity just "fall down", status bar is still up) and then it freezes... Looking forward to get this fixed soon.
€: And the boot time is horrible, before I see a screen it's black for idk 2 Minutes
€3: Nvm lol, actually the phone is now unable to boot in System....
€4: Give it a try with "optional" F2FS File system step, let's see.
Click to expand...
Click to collapse
Thank you, already did it... reflash recovery.img but by spflashtool. Now im inside twrp3.2.1...
Now its time to try install oreo and gapps

cedricboquiren said:
Should we come from the last 7.1.2 build (which has different partitions from stock)?
Click to expand...
Click to collapse
Yes, the latest 7.1.2 is mandatory. Added this to the first post now too.

I tried to install the new rom, after I installed the new twrp, the phone is still restarting, I tried to return to 7.1.2 with spft but no success even does not connect with the laptop, what I could do they do?

[ROM][UNOFFICIAL][8.1] LineageOS 15.1 for Amazon Fire HD8 7/6th gen (douglas/giza)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.Instructions:
Reboot to recovery mode
Wipe data, system (/system_root) and cache
Flash the ROM and the Gapps
Reboot and enjoy!
Downloads:
Builds: douglas - giza
GApps: OpenGapps (arm64/8.1/pico)
Reporting Bugs:
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Known issues:
Deep sleep (Doze)
Hardware decoding (OMX)
Camera (both photos/videos) isn't working on giza
Can't connect to hidden SSIDs
Notes:
SELinux is in Permissive mode
The ROM only supports both douglas (Fire HD8 2017) and giza (Fire HD8 2016)
How do i...
Unlock and install TWRP?
Follow the instructions of the unlock thread (douglas | giza)
Go back to the original/stock ROM?
Download the stock update.bin (douglas | giza) and flash it using TWRP
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Contributors
R0rt1z2, FreakyyLike (for the douglas donation)
Source Code: https://github.com/mt8163-dev
Kernel source: https://github.com/mt8163-dev/android_kernel_amazon_mt8163

⏱ Change log / Release Notes
2022-06-14 [douglas] [giza]
Updated sdcardFS to 2.0.
Updated the exFAT driver.
Fixed detection of external SDs.
2022-06-13 [douglas] [giza]
Rebased the entire tree, did a general cleanup
Fixed MicroG support (Signature Spoofing)
Fixed and re-enabled sdcardFS
Fixed direct Magisk installation/update
Enabled USB MIDI support
Enabled OTG ethernet support
Disabled binder logging
Enabled OpenGLES AEP
2022-01-02 [douglas] [giza]
Fixed USB tethering.
Added mediatek perf support.
Updated vendor blobs to the latest FireOS version.
Defined the vendor security patch.
2021-11-07 [douglas] [giza]
Fixed video recording on douglas.
2021-10-31 [douglas] [giza]
Fixed some DRM leftovers.
Added initial microG support.
Added exFAT support.
Fixed audio stream.
Added ged support.
Updated security patch to October 2021.
2021-10-03 [douglas] [giza]
Completely disabled sdcardfs.
Purged a lot of mtk/amazon logging.
Fixed missing symbols/libraries.
Reworked the audio configurations.
Fixed all the sensors.
2021-09-16 [douglas] [giza]
Fixed camera on douglas.
2021-09-12 [douglas] [giza]
Cleaned up wi-fi blobs/configs/service definitions.
Kanged the wi-fi HAL from a 8.1 mediatek device.
2021-09-07 [douglas] [giza]
Fixed swapped volume keys.
Show internal storage by default in the file manager.
Added option to reboot to hacked bootloader using ADB.
Disabled the update recovery function.
Added support for more SDs/USBs with other formats.
2021-09-05 [douglas] [giza]
Fixed over the air (OTA) updates.
Fixed Magisk/GAPPs installation.
The build is now signed with dev-keys.
Fixed installation of the ROM on giza.
Addressed a few SELinux denials.
2021-09-03 [douglas] [giza]
Audio works fine, incuding the mic.
DRM works fine, reports L1.
Video playback works partially fine.
Disabled camera as it doesn't work.

Reserved

Reserved

Rortiz2 said:
Magisk
For some weird reason, Magisk zip won't work (because of shims, wtf) so you'll need to manually patch your boot image with the Magisk Manager app and you'll need to flash it to boot_x with hacked fastboot mode or to boot with TWRP.
Click to expand...
Click to collapse
Fastboot is informed of the exploit so fastboot flash boot <path> will work.

SamDungUser said:
Fastboot is informed of the exploit so fastboot flash boot <path> will work.
Click to expand...
Click to collapse
No, fastboot isn't informed of the exploit, fastboot flash boot will overwrite the microloader and will brick the device.

Rortiz2 said:
No, fastboot isn't informed of the exploit, fastboot flash boot will overwrite the microloader and will brick the device.
Click to expand...
Click to collapse
Didn't know that. I think that's why I had to erase the boot partition just so I can install a rom again. it was able to boot to twrp so I just rebooted to hacked BL and erased then boot back and flash a rom in twrp

SamDungUser said:
Didn't know that. I think that's why I had to erase the boot partition just so I can install a rom again. it was able to boot to twrp so I just rebooted to hacked BL and erased then boot back and flash a rom in twrp
Click to expand...
Click to collapse
Yes that's possible, because TWRP restores the microloader (boot-exploit). Great to hear that you could recover it.

if you need to check the md5 upload the file and use https://emn178.github.io/online-tools/md5_checksum.html

The rom is abnormally large? When selecting the aroma package barely anything fits, in 7.1.2 it fit 5x more apps using th aroma package also 400 MB for the rom? what's causing this? how can I make the system partition bigger?

SamDungUser said:
The rom is abnormally large? When selecting the aroma package barely anything fits, in 7.1.2 it fit 5x more apps using th aroma package also 400 MB for the rom? what's causing this? how can I make the system partition bigger?
Click to expand...
Click to collapse
If I'm allowed to ask, what's aroma? And yeah, the ROM size it's quite normal since Android O includes vndk and hidls.

It feels really snappy compared to 14.1. I guess that's because of a different launcher?

dontpanic-xda said:
It feels really snappy compared to 14.1. I guess that's because of a different launcher?
Click to expand...
Click to collapse
I don't think the launcher has something to do with the snappiness. I guess Android Oreo it's more optimized than Android 7. You also need to keep in mind that I've updated the GPU drivers (kernel-side, mali).

Wow, great job @Rortiz2 ! Respect and thank you!

Rortiz2 said:
If I'm allowed to ask, what's aroma? And yeah, the ROM size it's quite normal since Android O includes vndk and hidls.
Click to expand...
Click to collapse
Aroma is an open gapps installer it includes all apps and offers a gui installer. Also, I found out what causes the screen issue. Apparently just installing a SELinux switcher app will cause the issue where if you put it to sleep by pressing the power button and you press the power button again to take it out of sleep nothing happens. I don't know how just installing a selinux switcher causes the screen issue and the Bluetooth crashes

SamDungUser said:
Aroma is an open gapps installer it includes all apps and offers a gui installer. Also, I found out what causes the screen issue. Apparently just installing a SELinux switcher app will cause the issue where if you put it to sleep by pressing the power button and you press the power button again to take it out of sleep nothing happens. I don't know how just installing a selinux switcher causes the screen issue and the Bluetooth crashes
Click to expand...
Click to collapse
Why would you set SELinux to enforcing..? Sepolicies aren't yet prepared to do so... Anyway, I don't have any clue about aroma, use the standard gapps package I guess.

Rortiz2 said:
Why would you set SELinux to enforcing..? Sepolicies aren't yet prepared to do so... Anyway, I don't have any clue about aroma, use the standard gapps package I guess.
Click to expand...
Click to collapse
I want to have it on enforcing to get safetynet to pass

SamDungUser said:
I want to have it on enforcing to get safetynet to pass
Click to expand...
Click to collapse
Alright, I guess I'll try to fix sepolicies then. Don't expect it to be quick though, this takes a lot of time.

I'm really impressed with this ROM. Running Services reports nearly 800 MB free after boot and it's definitely snappier. Also, viewing Settings with a pure black background is probably my favorite feature.
One thing I did run into was that during the install of GApps, it seemed to stall after the Installation Complete message. I just rebooted manually and it was all fine. Great job, Rortiz2

rom installs fine but it looks like it freezes after "installation compete" for opengapp.
Used the link above for openapp. Did not choose a different variation.

[ROM][BETA] LineageOS 19.1 for the Xperia Z5 Premium

LineageOS is a free and open-source operating system for various devices, based on the Android mobile platform.
Disclaimer:
It is your decision to install this software on your device. Neither LineageOS developers nor I take any responsibility for any damage that may occur from installing this software on your device.
{
"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"
}
Notes:
This rom does not come pre-rooted or bundled with any modifications or apps.
Download:
Android File Host | 7bf6035f8cca0560e6ec14d7b2a41621
Prerequisites:
- Make sure you're coming from firmware 32.4.A.1.54 before flashing this rom.
- Bootloader needs to be unlocked.
- Ensure that you have the latest version of TWRP recovery from here.
Install:
1) Reboot into TWRP Recovery.
2) Select Wipe -> Swipe to factory reset -> Advanced Wipe -> Dalvik /ART Cache, System, Cache and Data -> Swipe to Wipe.
3) Go back to TWRP's main menu -> Select Install -> Locate and choose lineage-19.1-202XXXXX-UNOFFICIAL-satsuki.zip file -> Swipe to confirm flash.
Bugs/Not Working:
- Camera
- Torch
- Touch vibration can sometimes be delayed.
- Please let me know if there is anything else.
If you encounter any other bug that are not mentioned in this list please provide a logcat and the steps necessary to reproduce the bug in detail (if necessary).
Sources:
Device Tree (Satsuki | kitakami-common/kernel/vendor)
XDA:DevDB Information
LineageOS 19.1, ROM for the Sony Xperia Z5 Premium
Contributors
Joel16, tarkzim, Berni-0815
ROM OS Version: Android 12
ROM Kernel: Linux 3.10.x
Version Information
Status: Beta
Current Beta Version: 20220912
Beta Release Date: 2022-03-20
Created 2022-03-20
Last Updated 2022-09-12

Change-logs:
20220912:
- Upstream lineage 19.1 changes.
- September 2022 security patches.
- Camera fixes by tarkzim.
- sepolicy updates by Berni-0815.
20220425:
- Upstream lineage 19.1 changes.
- Performance improvements in UI.
- April 2022 security patches.
20220320:
- Initial Release

Joel16 said:
LineageOS is a free and open-source operating system for various devices, based on the Android mobile platform.
Disclaimer:
It is your decision to install this software on your device. Neither LineageOS developers nor I take any responsibility for any damage that may occur from installing this software on your device.
View attachment 5566809
Notes:
This rom does not come pre-rooted or bundled with any modifications or apps.
Download:
Android File Host: ROM | d33aa8b4928652220f65b459f061aa27
Prerequisites:
- Make sure you're coming from firmware 32.4.A.1.54 before flashing this rom.
- Bootloader needs to be unlocked.
- Ensure that you have the latest version of TWRP recovery from here.
Install:
1) Reboot into TWRP Recovery.
2) Select Wipe -> Swipe to factory reset -> Advanced Wipe -> Dalvik /ART Cache, System, Cache and Data -> Swipe to Wipe.
3) Go back to TWRP's main menu -> Select Install -> Locate and choose lineage-19.1-202XXXXX-UNOFFICIAL-satsuki.zip file -> Swipe to confirm flash.
Bugs/Not Working:
- Camera
- Torch
- Touch vibration can sometimes be delayed.
- Please let me know if there is anything else.
If you encounter any other bug that are not mentioned in this list please provide a logcat and the steps necessary to reproduce the bug in detail (if necessary).
Sources:
Device Tree (Satsuki | kitakami-common/kernel/vendor)
XDA:DevDB Information
LineageOS 19.1, ROM for the Sony Xperia Z5 Premium
Contributors
Joel16, tarkzim, Berni-0815
ROM OS Version: Android 12
ROM Kernel: Linux 3.10.x
Version Information
Status: Beta
Current Beta Version: 20220320
Beta Release Date: 2022-03-20
Created 2022-03-20
Last Updated 2022-03-20
Click to expand...
Click to collapse
What a Great surprise ! Thanks a lot for the work. Will flash today and let you know about the bugs in a few days

Joel16 said:
LineageOS is a free and open-source operating system for various devices, based on the Android mobile platform.
Disclaimer:
It is your decision to install this software on your device. Neither LineageOS developers nor I take any responsibility for any damage that may occur from installing this software on your device.
View attachment 5566809
Notes:
This rom does not come pre-rooted or bundled with any modifications or apps.
Download:
Android File Host: ROM | d33aa8b4928652220f65b459f061aa27
Prerequisites:
- Make sure you're coming from firmware 32.4.A.1.54 before flashing this rom.
- Bootloader needs to be unlocked.
- Ensure that you have the latest version of TWRP recovery from here.
Install:
1) Reboot into TWRP Recovery.
2) Select Wipe -> Swipe to factory reset -> Advanced Wipe -> Dalvik /ART Cache, System, Cache and Data -> Swipe to Wipe.
3) Go back to TWRP's main menu -> Select Install -> Locate and choose lineage-19.1-202XXXXX-UNOFFICIAL-satsuki.zip file -> Swipe to confirm flash.
Bugs/Not Working:
- Camera
- Torch
- Touch vibration can sometimes be delayed.
- Please let me know if there is anything else.
If you encounter any other bug that are not mentioned in this list please provide a logcat and the steps necessary to reproduce the bug in detail (if necessary).
Sources:
Device Tree (Satsuki | kitakami-common/kernel/vendor)
XDA:DevDB Information
LineageOS 19.1, ROM for the Sony Xperia Z5 Premium
Contributors
Joel16, tarkzim, Berni-0815
ROM OS Version: Android 12
ROM Kernel: Linux 3.10.x
Version Information
Status: Beta
Current Beta Version: 20220320
Beta Release Date: 2022-03-20
Created 2022-03-20
Last Updated 2022-03-20
Click to expand...
Click to collapse
Ok i have flashed the rom and these are the things i have noticed so far:
- Selecting different choices for themes section depending on the extracted ones from Wallpaper does not exist which is probably LOS launcher's fault. (Couldn't flash any Pixel launcher mod as those i have tested caused launcher FC problem)
-There is a lag in Quick panel when editing, sliding it down or even pressing power button in Quick panel.
-When you wake the screen after being off, sometime the screen is blank, but if you power the screen off and turn it on again it will be fine.
-Sim detection takes a bit of a time like 1 or 2 mins after the phone boots sometimes(You can test maybe it's related to my signal, but i was fine in 18.1 or 17.1 which i was using just recently)
-Even tho vibration is disabled is settings, still some apps do have the vibration feedback with touch, like entering number in telegram or even AOSP's default keyboard.
-low volume on Mic when recording voice messeges in Telegram, WhatsApp (existed in your previous projects as well).
-Heating is fine, BUT you have restricted CPUs a lot in kernel side and i can't change those settings using kernel manager apps. This probably has effect on overall performance and will lead into lags in ui which i am facing now a bit sometimes (this was also the case with your latest 17.1 update)
-Battery icon in status bar is a bit too far from the edges of screen which i even noticed from your Screenshots as well (Not an important problem tho)
-unlocking animation for FP should start from the side power button but uses pixel 4 animation from the back FP sensor (again nothing very major lol)
In general functions for Daily driving this ROM is fine except for the camera you mentioned.
Thanks a lot for the new ROM. I know fixing these will take a while or some may not even get fixed. Take your time

alkh301180 said:
Ok i have flashed the rom and these are the things i have noticed so far:
- Selecting different choices for themes section depending on the extracted ones from Wallpaper does not exist which is probably LOS launcher's fault. (Couldn't flash any Pixel launcher mod as those i have tested caused launcher FC problem)
-There is a lag in Quick panel when editing, sliding it down or even pressing power button in Quick panel.
-When you wake the screen after being off, sometime the screen is blank, but if you power the screen off and turn it on again it will be fine.
-Sim detection takes a bit of a time like 1 or 2 mins after the phone boots sometimes(You can test maybe it's related to my signal, but i was fine in 18.1 or 17.1 which i was using just recently)
-Even tho vibration is disabled is settings, still some apps do have the vibration feedback with touch, like entering number in telegram or even AOSP's default keyboard.
-low volume on Mic when recording voice messeges in Telegram, WhatsApp (existed in your previous projects as well).
-Heating is fine, BUT you have restricted CPUs a lot in kernel side and i can't change those settings using kernel manager apps. This probably has effect on overall performance and will lead into lags in ui which i am facing now a bit sometimes (this was also the case with your latest 17.1 update)
-Battery icon in status bar is a bit too far from the edges of screen which i even noticed from your Screenshots as well (Not an important problem tho)
-unlocking animation for FP should start from the side power button but uses pixel 4 animation from the back FP sensor (again nothing very major lol)
In general functions for Daily driving this ROM is fine except for the camera you mentioned.
Thanks a lot for the new ROM. I know fixing these will take a while or some may not even get fixed. Take your time
Click to expand...
Click to collapse
Just so you know some of these are bugs from upstream, and will most likely be fixed by upstream lineage changes (not device tree related), others on the other hand will require some work whenever time avails.

Joel16 said:
Just so you know some of these are bugs from upstream, and will most likely be fixed by upstream lineage changes (not device tree related), others on the other hand will require some work whenever time avails.
Click to expand...
Click to collapse
Yes, for instance I know thet monet theme engine is LOS source related. But that device tree is pretty hard to work on.
Btw why don't you switch to OSS vendor?
I assume OSS can bring more stability and better overall performance. Even may fix some of the current bugs

flashed the rom, lets see what bugs we can find
thanks for another great work

alkh301180 said:
Yes, for instance I know thet monet theme engine is LOS source related. But that device tree is pretty hard to work on.
Btw why don't you switch to OSS vendor?
I assume OSS can bring more stability and better overall performance. Even may fix some of the current bugs
Click to expand...
Click to collapse
I'm all for open source but which ones are you referring to? I am testing lineage-17.1 with Sony's open source thermal manager. This rom however currently doesn't. Camera won't be easy, because there's too many Sony specific blobs that fails to communicate with any open source camera Hals. (Even with the Sony's OSS camera hal -- probably because our device wasn't initially targeted)

Joel16 said:
I'm all for open source but which ones are you referring to? I am testing lineage-17.1 with Sony's open source thermal manager. This room however currently doesn't. Camera won't be easy, because there's too many Sony specific blobs that fails to communicate with any open source camera Hals. (Even with the Sony's OSS camera hal -- probably because our device wasn't initially targeted)
Click to expand...
Click to collapse
I mostly meant LOS 19.1 and hmm, i didn't know you were using Sony's open source stuff
Well thanks for the info.

Thank u for maintaining this device for such a long period!

Thanks a lot

tnx for ur hard work
here geekbench result
highest multicore score of all z5p roms

niceeee

Nice work... waiting for the updated...bugs as mentioned

How to get into recovery

sanjuxox said:
Which gapps to be flashed?
Click to expand...
Click to collapse
opengapps

alisadeghian said:
How to get into recovery
Click to expand...
Click to collapse
unlock bootloader // flash twrp // power btn + vol down

newbiez5p said:
unlock bootloader // flash twrp // power btn + vol down
Click to expand...
Click to collapse
Recovery doesn't work with this rom.
I flashed this rom and after reboot i went to flash gapps, but
Can't go to recovery, got error while i tried to open it.
How to flash gapps

newbiez5p said:
opengapps
Click to expand...
Click to collapse
opengapps doesnt have android 12

Database Info

welcome