Database Info

Time to talk about Android O for our device

First question does Osprey's hardware support Android O ?

Prob does but we'll prob not be able to have some features

Osprey's hardware didn't supported android N too but we got it with custom rom... I think this will happened with android O too

Our device is in list to get los 15 ie. android O

androidbaba said:
Our device is in list to get los 15 ie. android O
Click to expand...
Click to collapse
Well that's a pleasant news. And considering the awesome dev support our device has, I'm pretty sure we'll be getting plenty of Android O ROMs to try out.

adityak1303 said:
Well that's a pleasant news. And considering the awesome dev support our device has, I'm pretty sure we'll be getting plenty of Android O ROMs to try out.
Click to expand...
Click to collapse
Just for fyi, lineageosdownloads.com is not the official site (download links are redirected to actual linageos.org (org, not com)). So information they give cannot be verified unless the official linageos blog posts something about it.
It's still a long way. Source code hasn't been out yet. After AOSP code is pushed, linageos team will work on it, but considering the limited resources (unlike CyanogenMod), it can take a while. After the base is ready, then devs will focus on building device specific images and fix bugs. Only then android o will be roaster ready. Other derivative ROMs will take more time obviously.
We can't be sure if 8.0 will be fully compatible with our device. We don't have official Nougat kernel sources and proprietary blobs (AFAIK), also from what I've observed so far, the farther apart the last official firmware and target firmware are, the harder it is to keep a ROM unmodified and yet stable & functional.
Our device shouldn't die that easy though, as newer Moto devices with similar hardware as osprey and Merlin have been released.
Broadcasted from Zeta Reticuli

Just like i say earlier our device it wasn't supported android N but we got it thanks to our awesome developers. I think they won't let us down with android O too.. it maybe take a little time but i think we will have android O for our moto g 2015
sorry for my bad english

Hopefully we get O, and hopefully O comes default with the pixel nav because redacting that would take effort thats not worth it now that nexus is dead .

Nikos dima said:
Just like i say earlier our device it wasn't supported android N but we got it thanks to our awesome developers. I think they won't let us down with android O too.. it maybe take a little time but i think we will have android O for our moto g 2015
sorry for my bad english
Click to expand...
Click to collapse
Our device does support Nougat, it is evident by the presence of custom ROMs (and even a stock port). The only reason we didn't get a OTA was because the company didn't provide us. The Moto ROM and these custom ROMs all are based on AOSP code.( Technically, if the company released the full source of their ROM and features, then we could build stock ROMs too)
And yes, you are right, it may take a little while but eventually we should see the ROMs coming
But the absence of latest device specific proprietary stuff and official kernel sources forces devs to look for other branches to fill the gaps and get newer thingies working. In some places it's not possible to implement a certain feature and an older feature is modded to make it work, for example before the official marshmallow OTA was out, we already got marshmallow ROMs but it had some hacky workarounds for radio (I don't know if it was updated after that), same goes for early Nougat when camera was becoming a problem. The camera is still not perfect (check linageos thread), working correctly on some apps and glitching on others. Newer software, newer challenges.
But codes are not exactly like food though, mixture of old and new ones is not always bad. But the blobs and drivers sometime give headache
Broadcasted from Zeta Reticuli

Have faith on our awsome developer we will surely have android O

Well, Android Oreo is out. I really hope that Osprey will get it soon.

https://source.android.com/devices/architecture/treble
according to this website,
"With Treble, a new stable vendor interface provides access to the hardware-specific parts of Android, enabling device makers to deliver new Android releases simply by updating the Android OS framework—without any additional work required from the silicon manufacturers"
Does this mean if someone gets Lineage OS 15 or OTA of Stock Android 8.0, they will receive all the updates from google from security patch to new Android versions (If the hardware is capable of running that version obviously!)?
---------- Post added at 09:47 AM ---------- Previous post was at 09:46 AM ----------
If that so, Manufacturers can just update all the devices which theoretically can run android O , it will be a onetime work, after that it'll be easy to update the devices

That would be amazing. Let's wait for a developer opinion.

I managed to build AOSP 8.0_r4 for osprey with SELinux disabled and tons of warnings, using cm14.1's files with some edits. Though for some reason the kernel doesn't seem to boot (I tried with linage os and squid kernel)
I attached the boot.img it built if someone more expert wants to look at it (I didn't manage to find anything wrong)
Flashing the file results in fastboot "Error: failed to load the kernel"

android1111 said:
I managed to build AOSP 8.0_r4 for osprey with SELinux disabled and tons of warnings, using cm14.1's files with some edits. Though for some reason the kernel doesn't seem to boot (I tried with linage os and squid kernel)
I attached the boot.img it built if someone more expert wants to look at it (I didn't manage to find anything wrong)
Flashing the file results in fastboot "Error: failed to load the kernel"
Click to expand...
Click to collapse
Hi, Alberto97 (the official maintainer of lineageOS for osprey) has successfully booted android O on osprey. If you can get in contact with him, he might help you.
PS. Don't bug him about ETAs. He'll release when he feels its ready.

adityak1303 said:
Hi, Alberto97 (the official maintainer of lineageOS for osprey) has successfully booted android O on osprey. If you can get in contact with him, he might help you.
PS. Don't bug him about ETAs. He'll release when he feels its ready.
Click to expand...
Click to collapse
Wow.. nice to hear this.. dude how do you know about this

rahul9999 said:
Wow.. nice to hear this.. dude how do you know about this
Click to expand...
Click to collapse
I follow him on G+. He posted the good news there.
https://plus.google.com/+AlbertoPedron/posts/Av6Knfnsja2

adityak1303 said:
I follow him on G+. He posted the good news there.
https://plus.google.com/+AlbertoPedron/posts/Av6Knfnsja2
Click to expand...
Click to collapse
Thanks For the information

I want to know about Merlin.. is it gonna get Android O? And if yes , when?

Abhishek17599 said:
I want to know about Merlin.. is it gonna get Android O? And if yes , when?
Click to expand...
Click to collapse
Hello,
There is no confirmation yet about this from official maintainer
Yes it should be get as Osprey already successfully booted it.. but don't ask for ETA

SM-G389F Marshmallow Port to SM-G388F

SM-G389F Marshmallow Port for SM-G388F
Hello Everyone,
So we all know that the SM-G389F has Marshmallow as it's OS,
But when we look on the side of the SM-G388F, we still have Lollipop as it's OS, So I decided to port the OS version of the SM-G389F to the SM-G388F while configuring it to be compatible with it's hardware! :laugh:
I might need some help....
But we can start by Converting the Firmware Download to a Zip for the Custom Recovery to flash it
(Link to Download)
Thanks for Tuning in,
I will keep you all Updated soon! :fingers-crossed:

Hello Everyone,
I've wasted plenty of time trying to extract the SM-G389F Marshmallow Firmware but it was all for nothing. So now I am asking you all who own this device to flash the ROM link above using odin (https://www.sammobile.com/firmwares/galaxy-xcover3/SM-G389F/BTU/download/G389FXXS1APK1/114774/) and then creating a backup via TWRP including the system.img and the boot.img and sending it to me via Dropbox, Google Drive...
Anyway I would like to forgive myself for failing to do this operation without owning the phone because of the md5 protection, but now I will be leaving this part in your hands
Thanks in Advice,
Diamond26

For all intents and purposes consider the two devices as completely separate/different. First of all the got completely different SoC's (not revisions but completely different brands of SoC's). I started try to compile LineageOS (my sources are up on github), but I was facing completely obscure or unheard of errors that where difficult to fix and the amount of free time I have has changed so I more or less have stopped doing that for the time being.
I will be writing up all the info I know off the device but that task has gotten away from me at the moment due to computer problems.

Matt07211 said:
For all intents and purposes consider the two devices as completely separate/different. First of all the got completely different SoC's (not revisions but completely different brands of SoC's). I started try to compile LineageOS (my sources are up on github), but I was facing completely obscure or unheard of errors that where difficult to fix and the amount of free time I have has changed so I more or less have stopped doing that for the time being.
I will be writing up all the info I know off the device but that task has gotten away from me at the moment due to computer problems.
Click to expand...
Click to collapse
Thanks for including yourself in this thread!
But may I ask which device do you own please?

Diamond26 said:
Thanks for including yourself in this thread!
But may I ask which device do you own please?
Click to expand...
Click to collapse
Well in currently typing it from my Samsung xCover3, with the Marvell SoC, so it's the SM-G388F

Matt07211 said:
Well in currently typing it from my Samsung xCover3, with the Marvell SoC, so it's the SM-G388F
Click to expand...
Click to collapse
Oh ok!
I was just eager to see if someone with a SM-G389F has come, maybe he could back up his 6.0 Stock ROM and maybe I could modify it.
That's why!

Diamond26 said:
Oh ok!
I was just eager to see if someone with a SM-G389F has come, maybe he could back up his 6.0 Stock ROM and maybe I could modify it.
That's why!
Click to expand...
Click to collapse
Please re-read my initial post in this thread, it's not possible. Your dealing with two different types of SoC's, so what your proposing is not possible, compiling from stock Android sources is (if you can fix every compile error)

Matt07211 said:
Please re-read my initial post in this thread, it's not possible. Your dealing with two different types of SoC's, so what your proposing is not possible, compiling from stock Android sources is (if you can fix every compile error)
Click to expand...
Click to collapse
I just want to mess around with the ROM, maybe I could modify something!

PixelBoot said:
I just want to mess around with the ROM, maybe I could modify something!
Click to expand...
Click to collapse
Do what ever you want, you can still mess around a lot, you just can't transplant files from the value edition to the Normal edition.
There is some cool mods you can do if you modify system apks.
https://forum.xda-developers.com/showthread.php?t=2799050

Is this thread still up?

Rrrrrrx404 said:
Is this thread still up?
Click to expand...
Click to collapse
Thinking about it...

I was thinking the same thing… I have an old Xcover, so i just wanted to try…
Did you succeed?

[ROM][T320][T325][UNOFFICIAL] LineageOS 16.0 | Android 9.0 Pie 20200411

I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
I'm using nano/pico gapps.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Work
Almost all
Known Issues
If you have wifi issues with latest release, please after install firmware apply patch:
SM-T320: https://drive.google.com/file/d/1E79Gcn7rNox2vP3OUd5FcVm2-a0aE12n/view?usp=sharing
SM-T325: https://drive.google.com/file/d/1fn1zJLL8dTJJJyoMEqph3DPH50YJp_gO/view?usp=sharing
Links
SM-T320
7. 20200411: march security patch, kernel update: https://drive.google.com/file/d/1I3QGfAEo55MKoEpBHBoZwj9a6EWzFBzA/view?usp=sharing
6. 20191211: december security patch, video recording, kernel from q with new wlan driver: https://drive.google.com/file/d/1YsniqI2RPwPKN9dB_7fKBAo9QkzxSFs_/view?usp=sharing
5. 20191130: latest sources, update kernel (autobrightness, some cleanup): https://drive.google.com/file/d/1swloB3vCfNsVzr9qsCmgpP8FpdrbXaJ2/view?usp=sharing
4. 20191112: november security patch: https://drive.google.com/file/d/1KQUcfna2rbeq8TLZfu44e63la59-rmzY/view?usp=sharing
3. 20191102: https://drive.google.com/file/d/1qJstVdMuPOM5ihsWqNvQeO4NyzsaVVIF/view?usp=sharing
2. 20191029: rollback dtb blocks to old stock: https://drive.google.com/file/d/1bY-vCQj57Gfgco1HeGbkkyjJEdOYOG2D/view?usp=sharing
1. 20191026: initial build: https://drive.google.com/file/d/1H3X036Qe9MJwEkE2zMPH5gQ05DLTkCzc/view?usp=sharing
SM-T325
4. 20200411: march security patch, kernel update: https://drive.google.com/file/d/13W9kC8RXK9CkqhDt5X9SQ7k9GISHbI5w/view?usp=sharing
3. 20191214: fix audio issues from last release: https://drive.google.com/file/d/1Mo3tPRTXtik2kBVNLJ8kw_bA6NJAgMuW/view?usp=sharing
2. 20191211: december security patch, ril + mobile data, internal speaker, kernel from q with new wlan driver: https://drive.google.com/file/d/13ARo1qiUh9MrNh9DHNlwxdo028cGpAjI/view?usp=sharing
1. 20191130: latest sources, update kernel (autobrightness, some cleanup), november security patch: https://drive.google.com/file/d/1Y4w1enXmMmDmLCvgzQSf5V6w-6wiPqLA/view?usp=sharing
Gapps
https://opengapps.org
Recovery
Use official version from:
SM-T320: https://twrp.me/samsung/samsunggalaxytabpro8.4wifi.html
SM-T325: https://twrp.me/samsung/samsunggalaxytabpro8.4lte.html
Sources
Sources: https://github.com/Lineageos
Device: https://github.com/Valera1978/android_device_samsung_mondrianwifi and https://github.com/Valera1978/android_device_samsung_mondrianlte
Kernel: https://github.com/Valera1978/android_kernel_samsung_msm8974
Vendor: https://github.com/Valera1978/android_vendor_samsung_mondrianwifi and https://github.com/Valera1978/android_vendor_samsung_mondrianlte
Thanks
Thanks to LineageOS team

Hello. 2 weeks ago with a big discount, I bought used a tab pro 8.4 wifi tablet.
I develop firmware for several tablets - note 12.2 on the same qcom 800, tab a 2016 on exynos 7870 (wifi&lte) and a tab s3 on qcom 820 (wifi&lte).
Initially, I thought, since the note pro is almost then same, as the tab pro series (actually, the note pro was develop based on the tab pro series), it turned out that these are huge differences, and I spent a huge amount of time to launch the tablet.
There were literally problems with everything - I spent almost a week launching just a panel and correctly turning it on/off. Then a huge amount of time to launch wifi and bt. Well, at the end, the sensors and cleanup the sources.
A bit later I'll build sm-t325 version and may be 10.1 sm-t525 (but I don't have this tablets, please send me to pm if you ready to help with test)
All my tablets already has android q. Of course after cleanups sm-t320 will get android q too.

Working for me only with pico gapps

del

Valera1978 said:
Hello. 2 weeks ago with a big discount, I bought used a tab pro 8.4 wifi tablet.
I develop firmware for several tablets - note 12.2 on the same qcom 800, tab a 2016 on exynos 7870 (wifi&lte) and a tab s3 on qcom 820 (wifi&lte).
Initially, I thought, since the note pro is almost then same, as the tab pro series (actually, the note pro was develop based on the tab pro series), it turned out that these are huge differences, and I spent a huge amount of time to launch the tablet.
There were literally problems with everything - I spent almost a week launching just a panel and correctly turning it on/off. Then a huge amount of time to launch wifi and bt. Well, at the end, the sensors and cleanup the sources.
A bit later I'll build sm-t325 version and may be 10.1 sm-t525 (but I don't have this tablets, please send me to pm if you ready to help with test)
All my tablets already has android q. Of course after cleanups sm-t320 will get android q too.
Click to expand...
Click to collapse
everything seems to work. thank you for this huge job

Thanks a lot! For me it works too!!! I used TWRP 3.2.3.0 and gapps mini (arm)! Dont forget a full wipe after installation.
Sent from my [device_name] using XDA-Developers Legacy app

@Valera1978
THX, you have done a great job, alot of us have waiting for this Version 16, camera works fine.

@Valera1978
Which Security Date has got this ROM.
Wound you like to update this ROM monthly with newest Patch level ?

bierma32 said:
@Valera1978
Which Security Date has got this ROM.
Wound you like to update this ROM monthly with newest Patch level ?
Click to expand...
Click to collapse
Current security update is october 2019.
You can monitor new update in: https://github.com/LineageOS/android_build/blob/lineage-16.0/core/version_defaults.mk , PLATFORM_SECURITY_PATCH define
Usually a new update appears on the 5-10th of the month (in lineage code) and after it I'm building new version.

Thank you for your working. I really expect the version of SM-T325

And what about SM-T520?

TechDriver said:
And what about SM-T520?
Click to expand...
Click to collapse
sm-t520 has differ platform. this is exynos5420 like t900\p900\901.

Thanks much! You brought a new life into my favorite tablet! It's hard to find a premium 8.4 tablet these days and hardware in this 5 year old one is running strong with your ROM.
Спасибо Валера!

Incredible to find developers still going strong in creating latest android version builds for this tablet after 5 years. Kudos to OP!
Works flawless and surely has added couple of more years life to the tablet now.

new versions.
Added version for sm-t325.
Unfortunately I do not have a t325 and I need somebody to test firmware. Please make backup efs/modem/may be all before test just in case.
Links in first post.

Valera1978 said:
new versions.
Added version for sm-t325.
Unfortunately I do not have a t325 and I need somebody to test firmware. Please make backup efs/modem/may be all before test just in case.
Links in first post.
Click to expand...
Click to collapse
I've tried test version on my SM-T325. There was repetitive rebooting problem initially and I cannot set anymore
However, thank you for your effort and I believe you can fix this problem.

How do i install this?
sorry to be a noob but this is my first time rooting an android device in about 8 years.
I have rooted by T320 and have super user.
I have installed the TWRP app.
I have odin.
I have all the downloads suggested on both my PC and my Samsung SD card.
WTF am i supposed to do from there? Do i install the mondrianwifi i find in the TWRP app if, so to boot or recovery? Or am i supposed to install the version the author linked. I hav read multiple articles but they don't explain what i am doing, why, how i should choose my options and they are all seriously out of date (given the age of the tablet)
Help!? Can someone give me a breadcrumb trail?
---------- Post added at 03:13 PM ---------- Previous post was at 02:51 PM ----------
scyto said:
sorry to be a noob but this is my first time rooting an android device in about 8 years.
Help!? Can someone give me a breadcrumb trail?
Click to expand...
Click to collapse
Ok i figured it out by a lot of poke and hope and got lucky.
I have the new firmware on with micro apps.
Was non intuitive how long the tablet takes after first reboot to get everything ready and WTF is that slider / circle animation - i thought it was telling me to slide my finger from right to left (that was up for like 2.5 mins the first time) luckily i just waited.
On first use lots of apps reported crashing most stopped but BT app was in infinite reboot.
Did hard reboot and the BT app is still infinitely rebooting along with android.process.media
Trying a factory reset, use TWRP to wipe device (all but SD card) and reinstall to fix....
---------- Post added at 03:32 PM ---------- Previous post was at 03:13 PM ----------
now its hung at the strange animation for more than 10 mins and power button does nothing? What next?
Another wipe and re-install not connected to USB seemed to fix it.

nrpia said:
I've tried test version on my SM-T325. There was repetitive rebooting problem initially and I cannot set anymore
However, thank you for your effort and I believe you can fix this problem.
Click to expand...
Click to collapse
Please post logs,

SM-T325 builds appreciated
Valera1978 said:
new versions.
Added version for sm-t325.
Unfortunately I do not have a t325 and I need somebody to test firmware. Please make backup efs/modem/may be all before test just in case.
Links in first post.
Click to expand...
Click to collapse
WOW just WOW 
 @Valera1978 Thank you for all your efforts and bringing this device back to life! I'm happily looking forward to test builds for the SM-T325 and provide logs if needed.

Valera, What is new in release from 11/02 (lineage-16.0-20191102-UNOFFICIAL-mondrianwifi)? Or it is targeted to owners of SM-T325 and you just misplaced it in SM-T320 section?

Guide to unlock your MEIZU 16 Series' bootloader

Update: DO NOT TRY TO PAY!!! THE GUIDE IS BADLY OUTDATED. JUST USE THE RESOURCES AND FREE METHODS.
If you want to try the paid method, you should definitely get in touch with the seller first. I don't know whether the previous sellers are active or not.
If you want to inform me of something important, please `@me`, (I missed many replies in the past years)
---
There seems to exist a new method: It is said to work on Qualcomm devices.
First, dump frp partion, then edit the value to 1 at 7fff0, finally, flash the modified frp image. then you can use fastboot command to unlock your phone.
This new method shall work for for ODM devices like 16T, 16x, 16xs and Note9 and so on. see FRP Method.
Below is the original post:
The original post has been removed, since it's outdated and I almost finished the English version tutorial on Github.
You can see it on github.
BTW, it's really difficult to use XDA's text editor.
You can download the TWRP of 16s here

it's a start, is there anyone who has already tried a gsi?

Good news for us Meizu users! Hope this is just a first step towards some good modding ?

Will this also work on Meizu Note 9?

adrxano said:
Will this also work on Meizu Note 9?
Click to expand...
Click to collapse
A new method has been released on 4pda, which supports almost all MEIZU devices using Qualcomm Proccessor. This is the original link 4pda.ru/forum/index.php?showtopic=961552&st=960#entry90949224

Loni626 said:
it's a start, is there anyone who has already tried a gsi?
Click to expand...
Click to collapse
I tried MIUI 11 and Flyme 8 , almost everything does not work on MIUI 11, it can boot into system, but the launcher doesn't work. Almost everything works fine on Flyme, except Bluetooth and Camera

I will try to rewrite an English version
The Chinese version has been moved to wiki, I'm planning to rewrite an English version similar to the Chinese version.

sukanka said:
The Chinese version has been moved to wiki, I'm planning to rewrite an English version similar to the Chinese version.
Click to expand...
Click to collapse
My firmware is 8.19.11.11 daily(16th Global device). Do i have a chance to unlock bootloader?

Lord Melkor said:
My firmware is 8.19.11.11 daily(16th Global device). Do i have a chance to unlock bootloader?
Click to expand...
Click to collapse
Sure, the new method applies to almost all devices, all versions. You can have a look at my github repository. I will edit the original post as soon as I can post links. BTW, is there any netdisk you guys use frequently? I don't know where to put the TWRP so that you can download easily.

sukanka said:
Sure, the new method applies to almost all devices, all versions. You can have a look at my github repository. I will edit the original post as soon as I can post links. BTW, is there any netdisk you guys use frequently? I don't know where to put the TWRP so that you can download easily.
Click to expand...
Click to collapse
You can use yandex.disk or google drive.
But you say about downgrade. Does the new method ignore the firmware version ?

Lord Melkor said:
You can use yandex.disk or google drive.
But you say about downgrade. Does the new method ignore the firmware version ?
Click to expand...
Click to collapse
yes, the new method applies to almost all versions, I have not updated the original post, because I have not prepared the English Version well on Github. You can have a look at github.com/sukanka/MEIZU16S_unlock_tutorial/wiki/Guide-to-Unlock-Your-MEIZU-Device

A new tutorial has been released on github
I must post in this way, as I'm not allowed to post links now. The Tutorial is at
github.com/sukanka/MEIZU16S_unlock_tutorial/wiki/Guide-to-Unlock-Your-MEIZU-Device
copy and paste this into your browser.

Any custom rom for meizu 16th without treble rom? And please add in phone cattegory meizu 16th on xda

inclr said:
Any custom rom for meizu 16th without treble rom? And please add in phone cattegory meizu 16th on xda
Click to expand...
Click to collapse
There seems to be custom ROMs for MEIZU 16th, I've seen Lineage, havoc, and mokee before. But i don't know how do these ROMs work. Anyway, I use 16s, not 16th. Besides, I don't know how to add a new phone category.
BTW, it's said that the kernel source of the 16 series will be released, maybe next year. And there are plans to upgrade the Android version of the 16 series.

sukanka said:
There seems to be custom ROMs for MEIZU 16th, I've seen Lineage, havoc, and mokee before. But i don't know how do these ROMs work. Anyway, I use 16s, not 16th. Besides, I don't know how to add a new phone category.
BTW, it's said that the kernel source of the 16 series will be released, maybe next year. And there are plans to upgrade the Android version of the 16 series.
Click to expand...
Click to collapse
Who said that?

inclr said:
Who said that?
Click to expand...
Click to collapse
a man who released some official ROMs that can be used to downgrade the firmware of the devices.

sukanka said:
I tried MIUI 11 and Flyme 8 , almost everything does not work on MIUI 11, it can boot into system, but the launcher doesn't work. Almost everything works fine on Flyme, except Bluetooth and Camera
Click to expand...
Click to collapse
You try another gsi rom? I want try pixel gsi or havoc, but I don't think was supported at 100%, probably lost taptic engine and other features... If have problems with this gsi and I want reinstall flyme stable, will be a problem?

Loni626 said:
You try another gsi rom? I want try pixel gsi or havoc, but I don't think was supported at 100%, probably lost taptic engine and other features... If have problems with this gsi and I want reinstall flyme stable, will be a problem?
Click to expand...
Click to collapse
No problem. If your phone becomes a brick, you can follow the unbrick tutorial to save your phone. But you are suggested to have glance at the tutorial before you go.
As reported by others, fingerprint and Mengine (taptic engine) don't work.

I am on havoc 2.9. Fingerprint mengine and mtp not work. But other features work fine

First telegram gruop for rom develop in meizu 16series: @Meizugsi
(nothing has been published yet, hopefully in the interest of some developers soon)

Suggestions..

Is anyone still using this device?
I'm planning to release a new build. Probably android 12 for now. Currently patching some sources, will be on GitHub soon. (No ETA please)
I don't have the device but I would need some testers.
Thanks.
(Only applies when there are demands on this thread)

if there are too many people using this device

nobodyAtall said:
Is anyone still using this device?
I'm planning to release a new build. Probably android 12 for now. Currently patching some sources, will be on GitHub soon. (No ETA please)
I don't have the device but I would need some testers.
Thanks.
(Only applies when there are demands on this thread)
Click to expand...
Click to collapse
ETA? XD im kidding.
I have this device as a main, the stock ROM sucks, so I made a fully comited attempt to either fix it or break it flashing ArrowOS, it got bricked unbricked and I managed to install ArrowOS at the end, I still have all the files I used in every step of the way.
Im a n00b but I would really like to learn some more about how phone modding works, I can be your tester if you want.
tell me if youre interested, also, how did you get started in all of this?

I have a secondary device and a sure way to return to a working state after mishaps, so I'd like to be a tester as well.

nobodyAtall said:
Is anyone still using this device?
I'm planning to release a new build. Probably android 12 for now. Currently patching some sources, will be on GitHub soon. (No ETA please)
I don't have the device but I would need some testers.
Thanks.
(Only applies when there are demands on this thread)
Click to expand...
Click to collapse
I always like to test new things so i can be your tester if you want