Database Info

[ROM][4.4.x][UNOFFICIAL][C8817D][MSM8916] MoKee OpenSource Project

Disclaimer:
Code:
All the firmwares, custom ROMs, official firmware updates, mods and tools mentioned here belong to their respective developers/owners.
You will be doing everything at your own risk.
We nor the developers cannot be held responsible if you end up damaging or bricking 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"
}
Introduction:
MoKee OpenSource is based on the Google AOSP. We update our source code frequently to keep up with the latest development, and not forgetting to merge in special features of our own at the same time.
A small group of people from around the world who are interested in Android launched this project on the 12th of December 2012, and is committed to make this ROM better and better. Like most contributors of open source projects (Omni, CyanogenMod, Slim AOSPA etc), we are doing all these in our free time as our passion...
Since this project is open source, anyone interested can participate in the development (maintain new devices, contribute code etc). Newcomers are always welcomed!
Read here for developer application; with this, you can host your unofficial MoKee builds on our server!
This is a build for a brand new MSM8916 device Huawei C8817D!
Features:
Odexed for faster performance (only in official releases, nightlies are deodexed)
Incremental updates
OTA updates - update on the fly!
Native exFAT support (Samsung devices only)
ListView animations
Multi window
Calendar - with lunar and solar calenders
Lunar calendar in lock screen
Task switching sidebar in recent apps (the list will increase if you install supported apps)
Bulk SMS recipients
Adjustable SMS font size
SMS sending delay
Smart dialing
Speed dialing
IP dialing
Custom carrier name
Network speed in status bar (upload and download!)
Built in timer in Apollo - determine when to stop playing music
MoKee Setup Wizard
Active Display
Adjustable navigation bar height
Unique Power Saver functions!
Custom screen off animations
Customizable recent apps shorcuts
Lockscreen notifications
Working CM11 theme engine
Many more! Since we are constantly adding new features, see changelogs to keep updated!
Screenshots
The screenshots below gets outdated very fast!
Multi-window:
Screen Off Animations:
Scale down:
Fade out:
Unique features:
Feature-rich settings:
Links:
Official Site:
http://www.mokeedev.com/en
Google Plus Community (join us for faster response!):
https://plus.google.com/communities/112433388317801966872
Statistics:
http://stats.mokeedev.com
Build Status:
http://build.mokeedev.com
Bug Tracker:
http://issues.mokeedev.com
Changelog:
http://changelog.mokeedev.com
GitHub:
http://github.com/MoKee
Kernel Sources:
https://www.codeaurora.org/cgit/qui...X_ANDROID_LNX.LA.3.7.2.1_RB1.04.04.04.157.010
Code Review:
http://review.mfunz.com
Unofficial Releases:
http://rom.mk/?device=c8817d&type=unofficial
Instructions For Incremental Updates:
http://forum.xda-developers.com/showpost.php?p=45438599&postcount=74
Incremental Updates For Unofficial Releases:
http://rom.mk/ota.php?owner=dianlujitao&device=c8817d&type=unofficial
MoKee Gapps (latest):
http://rom.mk/gapps
MoKee Gapps (full list):
http://www.androidfilehost.com/?w=files&flid=11492​
Donations:
All donations will be used for bandwidth and build server.
So yea, show some "MoKee lurve" here:
http://www.mokeedev.com/en/donations ​
Installation Instructions:
1. Wipe data/factory reset
2. Format /system
3. Flash ROM
4. Flash MoKee Gapps
5. Reboot​
Credits:
- MoKee Developers: https://github.com/orgs/MoKee/members
- CyanogenMod
- AOSP
- Koush for open-sourced SuperUser
- Slim Roms
- OmniROM
- @omkarsathe92 for the videos! ​
XDA:DevDB Information
Mokee Opensource, ROM for all devices (see above for details)
Contributors
dianlujitao, martincz
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: Mokee Opensource
Version Information
Status: Snapshot
Created 2014-10-29
Last Updated 2014-10-29

Full working?

Hi, would this work on ZTE V5 MAX MSM8916 ?

Hi
does it work with G620S wich is prety similar ?
best regards
seb

Hi!
This dont work on G620S
Give me an error 7

Thanks for.your job.
Could you get G620s source?
Regards.

All perfect except:
Main Camera not present.
Sub camera not present.

juandercito said:
All perfect except:
Main Camera not present.
Sub camera not present.
Click to expand...
Click to collapse
You can flash this rom on G620S ?
Can I have feedbacks please ?

alvinstarr said:
You can flash this rom on G620S ?
Can I have feedbacks please ?
Click to expand...
Click to collapse
Yes last nightly.
My smartphone is G620s-L01 version.

juandercito said:
Yes last nightly.
My smartphone is G620s-L01 version.
Click to expand...
Click to collapse
Ok, does everything work fine ?
Can you give me the exact version please ?

alvinstarr said:
Ok, does everything work fine ?
Can you give me the exact version please ?
Click to expand...
Click to collapse
No main camera, no rear camera, no nfc. Rest OK.

juandercito said:
No main camera, no rear camera, no nfc. Rest OK.
Click to expand...
Click to collapse
I tried to install but the recovery returned an error.
Does my phone get the good version to be flashed ?

Phone should be compatible. Yours is the same as mine. I had the error too but after flashing newer CWM version problem was gone.
Can't post links, swap xx with tt and get newer recovery:
hxxp://mega.co.nz/#F!K9YVxQ6I!MiibdItXb-y3F0wG2FJjWg
Bug: green videos in some players (Youtube)
Is OTG possible? Many users need it.

Hi dianlujitao!
First of all, thank you for your work. I have some questions, I hope you could answer them.
I'm from Hungary, and I just bought the phone last week. I had to unlock the bootloader, becasue T-Mobile branded it with too many programs, and unswitchabel startup / shutdown ringtones.
It's kind like the same solution as Alcatel devices, the Network provider brands the phones, and they have an individual partition on the phone's internal storage, so I have an additional partition /cust. I didn't managed to do a backup from this partition, because the provided CWM's fstab didn't mount or have this partition declared. I tired to modify the CWM-s fstab, to mount and backup this partition, but when I tried to boot the remade CWM, I've got errors from fastboot.It seems that I have to recompile the recovery with some specific header values, but I didn't find any information about that. Could you please help me out with this.
This is the same error message when I try to boot the repacked CWM recovery (with the modified fstab): http://forum.xda-developers.com/showthread.php?t=2428117
My second question is, If i will flash this ROM, and I'm not make a backup from /cust, this partition will be untouched when I finish flashing? I didn't find any information in the ROM's updater script to format this partition.
Mounts
Partitions
With GUI_1
With GUI_2
As you can see, /cust partition is a 744MB with ext4 filesystem, and it's mounted on 'mmcblk0p20'.
Thank You for Your help !

You need first unlock bootloader, then install CWM Recovery, and then imstall last nightly.

juandercito said:
You need first unlock bootloader, then install CWM Recovery, and then imstall last nightly.
Click to expand...
Click to collapse
I know, as I mentioned I've already unlocked and rooted the phone. (And I don't need to flash CWM, I just have to boot it via fastboot, and I can flash the latest nightly.) I'm just curious about the different partition layout.
Do you know what changed since jan17.? Then changelog doesn't show any new comments since then: http://review.mfunz.com/#/q/project:MoKee/android_device_huawei_c8817d

qltsar said:
I know, as I mentioned I've already unlocked and rooted the phone. (And I don't need to flash CWM, I just have to boot it via fastboot, and I can flash the latest nightly.) I'm just curious about the different partition layout.
Do you know what changed since jan17.? Then changelog doesn't show any new comments since then: http://review.mfunz.com/#/q/project:MoKee/android_device_huawei_c8817d
Click to expand...
Click to collapse
Sorry i didn't read all.
I haven't problems with fstab. Maybe making all wipes in recovery solve problems?
Since 17-jan there are no changes.

juandercito said:
Sorry i didn't read all.
I haven't problems with fstab. Maybe making all wipes in recovery solve problems?
Since 17-jan there are no changes.
Click to expand...
Click to collapse
You misunderstood me . I haven't got any problems with flashing via CWM, I'm just worried, because in Hungary we have an additional partition in our devices /cust, and the CWM not mounts it, because it's not declaired in the CWM's fstab, so i tried to change the fstab inside the recovery image, repack it, and then tried to boot it via fastboot I got an error message wich I mentioned at my first comment.

qltsar said:
You misunderstood me . I haven't got any problems with flashing via CWM, I'm just worried, because in Hungary we have an additional partition in our devices /cust, and the CWM not mounts it, because it's not declaired in the CWM's fstab, so i tried to change the fstab inside the recovery image, repack it, and then tried to boot it via fastboot I got an error message wich I mentioned at my first comment.
Click to expand...
Click to collapse
Also i have cust, in g620s-L01 version.
You need 05-dec date compilation of cwm recovery for solve problems.

juandercito said:
Also i have cust, in g620s-L01 version.
You need 05-dec date compilation of cwm recovery for solve problems.
Click to expand...
Click to collapse
I have this version: CWM_v2, and I didn't find mount/format /cust partition in the 'mounts and storage' menu, and if i make a backup, there is no cust.tar, therefore the CWM didn't mount the /cust partition.
If this is a wrong version that I linked above, could you please give me the right version of CWM wich handle the /cust partition?
Thank you !

[RECOVERY][DISCONTINUED] TWRP 3.5.0_9-0 [I9305]

{
"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"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.​
Code:
* [B][U]Your warranty is now void.[/U][/B]
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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.
Odin
- Odin3 v3.13.3
Heimdall
- Glass Echidna
TWRP for Samsung Galaxy S III (International LTE)
How to flash TWRP with Odin​1. If your phone is turned on normally, turn on Advanced reboot in Developer options and select "Download" from the Restart menu. Alternatively, power it off and press the Power, Volume Down, and Home buttons simultaneously. When the blue screen appears, release all 3 buttons and press Volume Up.
2. In Odin, import the appropriate twrp.tar file for your variant with the "AP" and press the "Start" button.
3. Pull the battery as soon as your phone vibrates.
4. You can then boot directly into TWRP by pressing the Power, Volume Up, and Home buttons simultaneously. Release all three buttons as soon as you see the boot screen ("Samsung Galaxy S III").
How to flash TWRP within a previous version of TWRP​1. If your phone is turned on normally, turn on Advanced reboot in Developer options and select "Recovery" from the Restart menu. Alternatively, power it off and press the Power, Volume Up, and Home buttons simultaneously. Release all 3 buttons when the boot screen appears ("Samsung Galaxy S III").
2. In TWRP, tap "Install" then "Install Image".
3. Navigate in the folder structure to the location of the appropriate twrp.img file for your variant and tap it.
4. Select the "Recovery" radio button.
5. Move the slider to the right to flash the TWRP image.
6. Tap "Reboot System" or, alternatively, tap the back arrow 3 times to return to the main menu, then tap "Reboot" and "Recovery" to reboot into the TWRP image you have just flashed.
Changelog
- See post #2.
Bugs
- You tell me!
Credits
- Option58, rgib, stek-kravari, and every other open source developer and user who contributes directly or indirectly to the TWRP community in the development of and in providing feedback for the i9305.
Sources
- Option58
- rgib
- i9305 repository
- TWRP repository
XDA:DevDB Information
TWRP 3.5.0_9-0, ROM for the Samsung Galaxy S III I9300
Contributors
ripee
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Stable
Current Stable Version: 3.5.0_9-0
Stable Release Date: 2020-12-28
Created 2018-01-27
Last Updated 2022-12-09

Reserved
CHANGELOG
The official build is now available!
* My thanks to everyone who tested my beta builds and left feedback

Reserved

Is there any difference between this twrp and @Option58 twrp?
https://androidfilehost.com/?w=files&flid=225362

stek-kravari said:
Is there any difference between this twrp and @Option58 twrp?
https://androidfilehost.com/?w=files&flid=225362
Click to expand...
Click to collapse
Other than the file size? I've seen his build but he doesn't have any publicly available device tree repo with which I could compare mine. If he adapted his build from any rom's source repos, mine should work as well as his. Two possible reasons for the difference in file size are a different compression method, or a different number and nature of entries in the BoardConfig.mk file, which contains the bare minimum hardware parameters and TWRP flags. Perhaps he included a few extra entries which may or may not be essential to the functionality of TWRP? Either way, I just want to contribute a TWRP device tree that could be used for future versions, as I intend on submitting it for official support just as soon as there is sufficient positive feedback. :good:

I just flashed your twrp and i could not boot up my phone, it gives me error:
Could not do normal boot, invalid kernel lenght

ripee said:
Other than the file size? I've seen his build but he doesn't have any publicly available device tree repo with which I could compare mine. If he adapted his build from any rom's source repos, mine should work as well as his. Two possible reasons for the difference in file size are a different compression method, or a different number and nature of entries in the BoardConfig.mk file, which contains the bare minimum hardware parameters and TWRP flags. Perhaps he included a few extra entries which may or may not be essential to the functionality of TWRP? Either way, I just want to contribute a TWRP device tree that could be used for future versions, as I intend on submitting it for official support just as soon as there is sufficient positive feedback. :good:
Click to expand...
Click to collapse
My sources are in the official LineageOS repo:
https://github.com/LineageOS/androi...mmit/e5734d09a16b97b7d55d3acf9d3e63e1b4653bd8
I didn't use any of the TWRP sources other than well...TWRP. Kernel, device tree and all that are from lineage-14.1.
Feel free to use it, might be more useful when next TWRP version arrives because I don't have build env set up anymore on my PC.

Option58 said:
My sources are in the official LineageOS repo:
https://github.com/LineageOS/androi...mmit/e5734d09a16b97b7d55d3acf9d3e63e1b4653bd8
I didn't use any of the TWRP sources other than well...TWRP. Kernel, device tree and all that are from lineage-14.1.
Feel free to use it, might be more useful when next TWRP version arrives because I don't have build env set up anymore on my PC.
Click to expand...
Click to collapse
That's exactly what I thought you did and the difference I described in my previous post. Both methods are equally correct, with the difference in file size being that the LineageOS BoardConfig.mk contains many more entries that are irrelevant for recovery mode. I know that both methods produce equally fully functional TWRP builds because I built TWRP for my tablet, gts210wifi, boths ways and both worked.
The reason why having a dedicated TWRP device tree is beneficial in the long term is that it's the preferred source code for submission for official support, given that the lack of unnecessary entries in the TWRP device tree reduces the chances that future versions of TWRP won't be able to be successfully built even with the backwards compatibility of the TWRP repo itself, omnirom/android_bootable_recovery. Less code, fewer bugs, fewer errors.
My other reason for building a dedicated TWRP device tree for i9305 is as a favor to a friend as well as the lack of a current official maintainer. Please report back whatever feedback you can and I will eventually submit it for official support.

ripee said:
That's exactly what I thought you did and the difference I described in my previous post. Both methods are equally correct, with the difference in file size being that the LineageOS BoardConfig.mk contains many more entries that are irrelevant for recovery mode. I know that both methods produce equally fully functional TWRP builds because I built TWRP for my tablet, gts210wifi, boths ways and both worked.
The reason why having a dedicated TWRP device tree is beneficial in the long term is that it's the preferred source code for submission for official support, given that the lack of unnecessary entries in the TWRP device tree reduces the chances that future versions of TWRP won't be able to be successfully built even with the backwards compatibility of the TWRP repo itself, omnirom/android_bootable_recovery. Less code, fewer bugs, fewer errors.
My other reason for building a dedicated TWRP device tree for i9305 is as a favor to a friend as well as the lack of a current official maintainer. Please report back whatever feedback you can and I will eventually submit it for official support.
Click to expand...
Click to collapse
Well I was just trying to fix bug where LineageOS OTA updates didn't work in the official TWRP. That's the main reason for this. It was only later when I found out official didn't boot. Make sure you include /misc partition please.
My personal opinion: I don't agree with that 'less code, fewer bugs, fewer errors' situation as you now have new TWRP device trees to maintain. Anyway building TWRP was not my main goal it's building lineage - but I can get easy TWRP whenever I want it. And this wasn't made for i9305 I don't even own i9305 - it's made for all smdk4412-common - that how I supported like 6 devices at once.
But, yeah, you can't use what I did for official TWRP and official TWRP needs to get fixed properly so thanks for you work Also if you notice anything wrong with the code in lineage (like wrong line or something) feel free to let me know.

Option58 said:
Well I was just trying to fix bug where LineageOS OTA updates didn't work in the official TWRP. That's the main reason for this. It was only later when I found out official didn't boot. Make sure you include /misc partition please.
My personal opinion: I don't agree with that 'less code, fewer bugs, fewer errors' situation as you now have new TWRP device trees to maintain. Anyway building TWRP was not my main goal it's building lineage - but I can get easy TWRP whenever I want it. And this wasn't made for i9305 I don't even own i9305 - it's made for all smdk4412-common - that how I supported like 6 devices at once.
But, yeah, you can't use what I did for official TWRP and official TWRP needs to get fixed properly so thanks for you work Also if you notice anything wrong with the code in lineage (like wrong line or something) feel free to let me know.
Click to expand...
Click to collapse
I don't own the i9305 either, I only have occasional access to one. I know very well that the smdk4412 source supports multiple devices, as I've also built TWRP for i9100.
As for Lineage, I've built for i9305 from its official repos in the past myself. It worked then so I'm sure your recent builds work just fine as well.

@ripee I just flashed your twrp and i could not boot up my phone, it gives me error:
Could not do normal boot, invalid kernel lenght

stek-kravari said:
@ripee I just flashed your twrp and i could not boot up my phone, it gives me error:
Could not do normal boot, invalid kernel lenght
Click to expand...
Click to collapse
Ok thanks for letting me know! I will let you know when the revised build is available.

stek-kravari said:
@ripee I just flashed your twrp and i could not boot up my phone, it gives me error:
Could not do normal boot, invalid kernel lenght
Click to expand...
Click to collapse
New build is up! Rather than taking partition values from the i9305 device tree, I took them from the smdk4412-common tree. Thank you, Option58, for your advice that proved to be correct.

ripee said:
New build is up! Rather than taking partition values from the i9305 device tree, I took them from the smdk4412-common tree. Thank you, Option58, for your advice that proved to be correct.
Click to expand...
Click to collapse
Link?

stek-kravari said:
Link?
Click to expand...
Click to collapse
OP

@ripee With new version now the phone loops samsung logo

stek-kravari said:
@ripee With new version now the phone loops samsung logo
Click to expand...
Click to collapse
I'll take another look, thank you!

Ok, try it now. I had the wrong board kernel pagesize in the BoardConfig.mk.

ripee said:
Ok, try it now. I had the wrong board kernel pagesize in the BoardConfig.mk.
Click to expand...
Click to collapse
Same thing again

stek-kravari said:
Same thing again
Click to expand...
Click to collapse
Try again please.

Free-Droid - One-Click Rom Installation Assistant

Code:
I am not responsible for any damage resulting from the use of the Free-Droid software.
Free-Droid is now Anarchy-Droid
Free-Droid has been fully rewritten from scratch in go and is now published as Anarchy-Droid. This page is kept for reference only. Please follow the link and use the new version of this software.
Introduction
Free-Droid is an application designed to help you install custom roms on your Android device. It is supposed to make the process of finding, downloading and installing a rom (with addons like Magisk, F-Droid and microG) as easy as possible. The primary audience is all the folks who do not really know anything about Android, TWRP or roms, but still would like to run a free, open-source and non-bloated Android on their devices. Using a free after-market rom like LineageOS should not be restricted to the few people with enough technical know-how to do the complex installation procedure all by themselves.
Free-Droid is free and open-source and is available for Windows, Mac and Linux. As of now, it should be working fine with Samsung, OnePlus, NVidia, Sony and Motorola devices and with all other devices that already have TWRP installed.
Download
Download from the official website.
Images
{
"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"
}
What it does
help you activate USB debugging
help you install drivers
help you unlock the bootloader
download and install TWRP
update TWRP if a newer version is available
download and install a rom
download and install F-Droid and MicroG
download and install Magisk (legacy method, off by default)
Features and explanations
Please visit the Gitlab page of the project for more details!
Compatibility
Free-Droid is supposed to work on as many devices as possible. Supported brands as of now are:
Samsung
Motorola
Oneplus
NVidia
Sony
Every device that already has TWRP installed: launch Free-Droid, boot your device into TWRP and connect it with USB to your computer
For the support status of a specific device, you can enter its model name here to check the compatibility.
The Free-Droid application itself will tell upon device connection if it is compatible. If it says that your device is not supported, you can be sure that it will not work. As of now, Free-Droid will display device untested for most devices, because I will only mark a device as supported if a few people tested it and confirmed it is actually working fine.
Changelog
For a changelog please just have a look at the commits on gitlab.
Beta
Although Free-Droid already runs very well, I was not able to test it on a lot of computers and with many different devices. Therefore, consider Free-Droid to be beta software for now.
Besides, there are a few things that still need to be implemented. What is not working yet:
project treble roms
devices that need special treatment like storage repartitioning
Finally, in order to lead Free-Droid out of the beta phase of development, a lot of testing needs to be done. This way, Free-Droid will know more reliably which devices can be expected to be workable without issues and which ones it should deny to work on.
Further development plans
add support for more brands that can be easily unlocked
handle project treble GSI roms
add a button to abort a running installation procedure
create packages for 32 bit computers
add MoKee rom
add /e/ rom
add possibility to install openGapps instead of microG ?
add possibility to select an additional zip to flash after the rom ?
fix crash on windows if changing folder on rom selection dialog
add a way to backup and restore using TWRP ?
add more documentation to the gitlab page ?
A note about Magisk installation
Installing magisk is getting more and more difficult. The installation method employed by Free-Droid is now discouraged and called a legacy installation method, because it can cause trouble and break the ability of the system to boot. For that reason, the installation of Magisk is turned off by default now in Free-Droid and a warning is issued to the user when turning it on.
You can still try to install Magisk with Free-Droid during the normal installation procedure. But if your system does not boot afterwards, you will have to try again without Magisk. On some devices, you might need to know how to manually boot into recovery in order to retry the installation (device-specific hardware key combination).
Free-Droid now also provides an easy way to try and install Magisk later on. The same ("legacy") installation method is used, but you can try the installation after the first boot of your newly installed system. I've seen a case where this would work while installing Magisk before the first boot would not work. This assumes that TWRP is connected or at least still installed.
I need you
Please test Free-Droid on your computer and with your device.
In case of issues: use the button in Free-Droid to pack a bug report and either send it with an email or create an issue on the gitlab issue tracker.
If you have a device of a supported brand for which Free-Droid does not find a rom by itself, please leave me a message with a link to a working rom (and/or TWRP image). If you can confirm that the rom is stable and fully working, I will add it to the Free-Droid unofficial archive and it will become available in Free-Droid.
If you know about a faulty official release of TWRP or a rom, please also leave me a message. Example: the latest few official releases of TWRP for i9305 (Samsung Galaxy S3 LTE) are faulty and fail when trying to install a rom with sideload. Free-Droid uses a specific version of TWRP in that case and can automatically handle cases like that in general. I just need to know which devices need a workaround.
Thanks To/Credits
LineageOS
Resurrection Remix
Omnirom
CarbonROM
AOSPExtended
TWRP
MicroG
F-Droid
Aurora
Magisk
NanoDroid
XDA for being the one and only place for custom android stuff
You and the rest of the XDA community for helping make Free-Droid better
XDA:DevDB Information
Free-Droid, Tool/Utility for all devices (see above for details)
Contributors
imska
Source Code: https://gitlab.com/free-droid/free-droid
Version Information
Status: Beta
Created 2019-07-01
Last Updated 2021-04-09

Reserved

download for linux coming soon ?

Exodusnick said:
download for linux coming soon ?
Click to expand...
Click to collapse
Download for Linux is already there.
Download for Mac coming soon (as soon as I figure out how to create a mac-app with a bundled jdk and launchable by click)

Download for Linux 404 Not Found
https://free-droid.com/
Downlad for Windows yes for Linux no

Exodusnick said:
Download for Linux 404 Not Found
https://free-droid.com/
Downlad for Windows yes for Linux no
Click to expand...
Click to collapse
You're absolutely right, thanks for pointing that out!
Fixed.

Ladies and Gentlemen,
Mac support has landed. You can now download Free-Droid for MacOS.
Depending on your Gatekeeper settings, you might need to launch Free-Droid by right-clicking on it and selecting Open. If it still fails to start, try to start the file called "right-click open" in the same way.

It is out and works with Ubuntu 18.4.2 and a Galaxy S5 (kltedv). Can Take a bit to download and install all of its Binaries .... A bit like Odin look. Similar to Skipsoft, with out a huge amount of reading.
Version 0.6.6 ; build 20190723; Lic-GPL-3.0
keep up the work on this! Seems rather easy to use.
Will keep an eye for updates coming..

This is beatiful! I wasted probably 2 hours this morning to get a android 9 on my old s5 since i need it for a project, i'm not a complete newby, i rooted and changed rom many time in the last 8 years but i do it every once in a while, so i always have to check for tutorials again and there is alwasy some step that don't go as planned, as today the rom was not installing, was almost ready to give up to not lose more time, saw this, was almost sure this would gone wrong somewhere as all automated stuff while after a couple of clics and 5/10m my s5 was ready with android 9 on it. THIS IS JUST BEATIFUL and great, hope it gain the visibility it deserve!
Really GREAT job!

Ladies and gentlemen,
Support for OnePlus devices has landed.!
Assuming that the bootloader unlock procedure is the same on all OnePlus devices, Free-Droid should work perfectly with them now. Still, any bug report is welcome.
Developed and tested with a OnePlus X (onyx).
Happy flashing to everyone!

Fixed bug when connecting device on the latest release.
Pushing update to the server right now, just restart the application and let it update itself.

Sorry for the server downtime over the last days. Everything is back online again and running.
Update to be released soon with support for nvidia shield tablet (will need testing though).

0.7.3 update released
-Better device detection using a database from here. This should result in less devices not recognized at all. Still, a lot of devices may be recognized, but have no working TWRP or rom known to free-droid.
-a lot of refactoring done in the code
-initial support for NVidia devices. Sould work in theory, but I couldn't test it by myself yet.

Says Device Supported. Then Says "Sorry, I don't know how to work with your device." Samsung Galaxy S5 SM-G900V.

DKDK99 said:
Says Device Supported. Then Says "Sorry, I don't know how to work with your device." Samsung Galaxy S5 SM-G900V.
Click to expand...
Click to collapse
Thanks for reporting this. Maybe you can help me sort this out... The G900V is the Verizon variant if I'm not mistaken. Can you confirm that it *should* work with the official lineageOS for the S5 (klte)? Besides, it would be of great help for me to diagnose and fix the error if you could send me the logs of free-droid. You can hit export logs in the help page of the application and drop the zip either here or send to [email protected]

New update released: 0.7.5
Sony support!
better device recognition
bug fixes

hope u can add support to install custom rom other than Pie 9.0. Coz I want to install stable version of Xposed.

You already can install any ROM you have downloaded. Just select "use my own ROM" and choose the zip.
But I think you can use magisk and the module called tai chi to install and use xposed stuff

Linux Version
@imska
Stuck forever at "Welcome Screen" on Ubuntu 16.04 (Xenial fork)

Looks amazing don't have a chance to test it but here are some mirrors:
Windows https://www.mediafire.com/file/1603rruccyef7gv/Free-Droid-WIN-latest.zip/file
Mac https://www.mediafire.com/file/qi64ju4y7108nqc/Free-Droid-MAC-latest.tar.gz/file
Linux https://www.mediafire.com/file/m5hzx7b4xie503o/Free-Droid-LINUX-latest.tar.gz/file

TWRP 3.4.0 for the Samsung Galaxy Fold

TWRP 3.4.0 for the Samsung Galaxy Fold
{
"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"
}
Introduction
It gives me great pleasure to present to you TWRP on the Samsung Galaxy Fold. Your foldable phone just became even more flexible.
This project picks up TWRP where Chris Williamson left off. Chris produced the initial release of TWRP for the Fold, which combined a custom kernel sporting some extra features with a pre-rooted TWRP image.
Chris asked me to take over the development of TWRP for the Fold to allow him to concentrate on kernel development for the device, and I was happy to oblige. My goal is to offer you the most functional build of TWRP that I possibly can, whilst making no assumptions about your desire to root the device or run a custom kernel. For that reason, the kernel I am supplying as part of this project is as close to stock as possible, with only the minimum number of changes required to allow TWRP to function, and with no added features. For the same reason, the images I provide have not been pre-rooted with Magisk.
Rooting Samsung system-as-root devices
How you root your Fold depends on whether you are running Android 9 (Pie) or Android 10. If, however, you have already upgraded your device to Android 10, you can root your device only in the boot partition. For reasons that are not yet clear, the Fold will not boot Android froma custom kernel that is rooted in recovery.
Rooting in the recovery partition
When the device is rooted in recovery, the TWRP image must be patched with Magisk (using the Magisk Manager app) to allow the same kernel to be shared between TWRP and Android. After patching, the user always boots the device from the recovery partition, and uses the device's hardware keys at boot time to select between Magisk-rooted Android and TWRP. A normal system boot from the boot partition brings the system up without root.
Rooting in the boot partition
When the device is rooted in the boot partition, the TWRP image is left untouched. Instead, the boot partition must be rooted with Magisk by flashing the Magisk zip file in TWRP. Rooted Android is booted via a normal system boot and the hardware keys play no special role. There is no option to boot Android unrooted.
Device preparation
Before doing anything else, back up your data now if you have any.
If you are installing TWRP on a brand new device, you must first unlock its bootloader. Select OEM Unlocking from Settings → Developer Options, then reboot to Device Unlock mode to actually unlock the bootloader. This will have the side-effect of resetting the device.
If you are installing TWRP on an unrooted device, it is crucial that you also flash the attached vbmeta.img file at the same time. Simply include this in a tar file with the TWRP image for your device (renamed recovery.img) and flash them together. You must reformat /data after doing this.
If you fail to neutralise the device's vbmeta protection before rebooting, the device's anti-tampering protection will be triggered and you will be unable to boot either Android or TWRP. A full reinstallation of stock firmware will be required and your device may be left in KG State Prenormal, requiring time-consuming extra steps to restore its ability to accept unofficial images again. Do not fail to neutralise vbmeta.
If you have already rooted your device with Magisk, vbmeta has already been disarmed and you may proceed with installing TWRP.
Image preparation
Rooting in the recovery partition
As noted above, the TWRP images supplied here are not pre-patched with Magisk. If you wish to dual-boot TWRP and Android Pie, you must patch the recovery image with Magisk before flashing it. Version 20.2 of Magisk is recommended for this. Versions 20 and 20.1 contain a serious bug that will render the recovery partition unbootable after patching. Please see John Wu's excellent step-by-step instructions for rooting the 2019 generation of Samsung Pie devices with Magisk.
An altogether simpler way of working is to flash the TWRP image on demand, only when required. After finishing your work in TWRP, simply replace TWRP with a Magisk-rooted stock recovery image and reboot to Android. I personally recommend this swapping approach, as it frees both the TWRP maintainer and the user from constantly updating the TWRP image to ensure it contains a kernel that is compatible with the version of the firmware on the device.
Here is a basic sample script that will check whether the current environment is Android or TWRP, flash the appropriate recovery image for the other environment, then reboot to it. You can easily adapt it to fit your needs.
Code:
twrp_img=/sdcard/twrp/twrp-3.3.1.img
stock_img=/sdcard/twrp/recovery-ask2-magisk.img
if [ -f /sbin/magisk ]; then
# We're in Android: Switch to TWRP.
#
infile=$twrp_img
else
# We're in TWRP: Switch to Android.
#
infile=$stock_img
fi
dd if=$infile of=/dev/block/by-name/recovery bs=$(stat -c%s $infile) && reboot recovery
Rooting in the boot partition
No special image preparation is required for installation on Android 10 devices.
TWRP images
TWRP is offered here as an assortment of recovery image files. To use with Odin, first rename the appropriate file recovery.img and then tar it. Ready-made tar files are not supplied here, because it would double the number of files to be maintained, and because it's trivial to generate a tar archive on any modern computing platform, including on the Fold itself.
Post-installation
The Fold, like all 2019 Samsung devices, utilises file-based encryption (FBE) by default. The use of encryption in TWRP on Samsung devices is invariably problematic, however, and encryption is therefore routinely disabled by users wishing to use TWRP. If this is not done, your files will remain unreadable to TWRP.
To remove encryption from your device, please flash the Samsung multi-disabler after installing TWRP, and then reformat /data again. Do not skip this step, even if you have already formatted /data one or more times thus far. If installing TWRP on Android 10, you need at least v2.3 of the multi-disabler.
Compatibility
The images below are known to be compatible with the firmware revisions stated. Results on other revisions will vary.
The F907B images have been personally tested and verified by me on my own Fold 5G prior to release. The F900F images should be of comparable quality.
Download
Android 10
Latest release for F907B (BTH2 firmware)
twrp-winnerx-3.5.0_9-1_ianmacd.img
twrp-winnerx-3.5.0_9-1L_ianmacd.img (landscape)
Latest release for F900F (BTH2 firmware)
twrp-winner-3.5.0_9-1_ianmacd.img
twrp-winner-3.5.0_9-1L_ianmacd.img (landscape)
Android 9
Latest release for F907B (ATA1 firmware)
twrp-winnerx-3.3.1-23_ianmacd.img
twrp-winnerx-3.3.1-23L_ianmacd.img (landscape)
Latest release for F900F (ATA3 firmware)
twrp-winner-3.3.1-23_ianmacd.img
twrp-winner-3.3.1-23L_ianmacd.img (landscape)
Known problems
TWRP is currently displayed only on the device's main (inner) screen.
Haptic feedback is currently unavailable in TWRP.
Frequently Asked Questions
Q. Why do you offer a separate build for each device with landscape orientation?
A. The aspect ratio of the main (inner) screen 4.2:3 is such that TWRP on this device looks good in both portrait and landscape orientation. In portrait mode, the clock and battery meter are shifted to the left to avoid the camera notch. In portrait mode, the entire image is shifted to the right to avoid the notch.
See the gallery of images below, or simply try each version of TWRP on your device, to discover which orientation you prefer.​
TWRP source code
TWRP bootable recovery
TWRP device trees
Galaxy Fold a.ka. winner (F900F)
Galaxy Fold 5G a.ka. winnerx (F907B)
Kernel source code
Galaxy Fold a.ka. winner (F900F)
Galaxy Fold 5G a.k.a. winnerx (F907B)
Real-time chat
For support or just to talk about the device amongst friends, please join our small Telegram group dedicated to the Galaxy Fold.
Credits
I am indebted to Chris Williamson (@chrisaw) for laying the foundations for TWRP on the Fold. And thanks in no small part to him and his contagious enthusiasm for the device, I'm now also indebted to Samsung for the purchase price of a Fold 5G.
Thanks to @osm0sis for AIK, a tool without which working with boot images would be far more tedious than it already is.
Thanks to Samsung for engineering this amazing device in the first place.
And last but not least, thanks to my wife, Sarah, for her tolerance of my expenditure on gadgetry.
XDA:DevDB Information
TWRP for the Samsung Galaxy Fold, Tool/Utility for the Samsung Galaxy Fold
Contributors
ianmacd, chrisw
Version Information
Status: Stable
Current Stable Version: 3.4.0-4_ianmacd
Stable Release Date: 2020-10-05
Created 2019-11-20
Last Updated 2021-01-19

Gallery
Unlocked bootloader stage 1
Unlocked ootloader stage 2
Main menu
Making a back-up (in Dutch)
Main menu (landscape)
Instaling an image (landscape)

Changelog
3.5.0_9-1_ianmacd
Update to TWRP 3.5.0.
3.4.0-4_ianmacd
Use latest F907BXXS4BTH2 and F900FXXS4BTH2 kernel source code.
3.4.0-1_ianmacd
TWRP updated to version 3.4.0.
3.3.1-101_ianmacd
Use latest F900FXXU3BTDD and F907BXXU3BTDD kernel source code.
Kernel now built using clang 8.0.11.
3.3.1-100_ianmacd
First release supporting Android 10.
Use latest F900FXXU3BTCD and F907BXXU3BTC9 kernel source code.
3.3.1-23_ianmacd
Use latest F900FXXS3ATA3 and F907BXXS3ATA1 kernel source code.
3.3.1-22_ianmacd (F907B only)
Build kernel from latest F907BXXS2ASL3 source code.
3.3.1-21_ianmacd (F907B only)
Build kernel from latest F907BXXU2ASK9 source code.
3.3.1-20_ianmacd
Use latest F900FXXS2ASKC and F907BXXS2ASK2 kernel source code.
Build without crypto code, as crypto is unsupported.
MInor fstab fix for /data.
Disable sundry irrelevant kernel features for a slightly leaner kernel.
3.3.1-17_ianmacd
First ianmacd release, using F900FXXU1ASJ4 and F907BXXS2ASK2 kernel source code.

That was fast!
Sadly most of us can't afford this 2000$ phone lol

Selling my US version, time to get F900F

Version 3.3.1-20_ianmacd released.
This release upgrades the kernel from the latest Samsung source code. In the case of the F900F, there are significant changes, whereas the F907B's kernel is hardly differs from the previous version.
The builds have also been stripped of superfluous crypto code, and a harmless bug in the fstab has been fixed.
3.3.1-20_ianmacd
Use latest F900FXXS2ASKC and F907BXXS2ASK2 kernel source code.
Build without crypto code, as crypto is unsupported.
MInor fstab fix for /data.
Disable sundry irrelevant kernel features for a slightly leaner kernel.

ianmacd said:
This release upgrades the kernel from the latest Samsung source code. In the case of the F900F, there are significant changes, whereas the F907B's kernel is hardly differs from the previous version.
The builds have also been stripped of superfluous crypto code, and a harmless bug in the fstab has been fixed.
3.3.1-20_ianmacd
Use latest F900FXXS2ASKC and F907BXXS2ASK2 kernel source code.
Build without crypto code, as crypto is unsupported.
MInor fstab fix for /data.
Disable sundry irrelevant kernel features for a slightly leaner kernel.
Click to expand...
Click to collapse
Thank you for all your work !!!

help me plz
hello, I can't flash with Odin because it gives me an error message: blocked from the OEM.

Version 3.3.1-21_ianmacd released for the F907B.
Changelog
3.3.1-21_ianmacd (F907B only)
Kernel built from latest F907BXXS2ASK9 source code.

Hi ianmacd
I know this is off top, but couldn't private message you
On libsecure_storage companion for rooted Samsung devices ver. 2.0 I experienced strong connectivity issues with airpods 2 (on note 9), rolling back to 1.8 got working it ok. Just for your information

DTman22 said:
hello, I can't flash with Odin because it gives me an error message: blocked from the OEM.
Click to expand...
Click to collapse
Same here.. anyone can help ...?

Version 3.3.1-22_ianmacd for the F907B released.
Changelog
3.3.1-22_ianmacd (F907B only)
Build kernel from latest F907BXXS2ASL3 source code.

hi I tried to use the method but something wrong happened, now my f900f stuck on starting android and it won't start up .
how can I go to download mode .?
Note: the VOL_UP + Power bottom it's not doing anything, even if putting the cable into the phone while starting up ..
any solutions .. ?

I'M getting "custom binary blocked by OEM lock "
the OEM unlock in developer option is ON
model F900F
Any solution ?

thmthoom said:
I'M getting "custom binary blocked by OEM lock "
the OEM unlock in developer option is ON
model F900F
Any solution ?
Click to expand...
Click to collapse
All you have done by toggling that option under Developer Options is enable OEM-unlocking of the device. You haven't actually opened the lock yet.
Boot to Download Mode to actually open the lock.
See the OP for more details.
Sent from my SM-N975F using XDA Labs

ianmacd said:
All you have done by toggling that option under Developer Options is enable OEM-unlocking of the device. You haven't actually opened the lock yet.
Boot to Download Mode to actually open the lock.
See the OP for more details.
Sent from my SM-N975F using XDA Labs
Click to expand...
Click to collapse
Thanks for your response brother..
Actually I’m booting to download mode using K 300 tool .. because I cannot boot using VOLUP + POWER bottom .. so my question is :
1- how to open the lock through the download mode , coz I’m not getting any options there.
2- what do u mean by “ see the op for more details “

ianmacd said:
All you have done by toggling that option under Developer Options is enable OEM-unlocking of the device. You haven't actually opened the lock yet.
Boot to Download Mode to actually open the lock.
See the OP for more details.
Sent from my SM-N975F using XDA Labs
Click to expand...
Click to collapse
Brother , for Unlocking Bootloader these are the steps :
Allow bootloader unlocking in Developer options → OEM unlocking ( DONE )
Reboot your device to download mode. Either use adb reboot download, or use the key combo for your device. ( DONE )
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot. ( the volume up won't work in this step, only I can use Volume down+power to restart the phone )
So what to do in this case if you have any ideas ...

I Followed " John Wu's excellent step-by-step instructions for rooting the 2019 generation of Samsung Pie devices with Magisk. " STEP-BY-STEP these was the resutls :
1- I won't able to use VOL_UP bottom , I skip this step " I think this step caused me a lot of problems "
2- all other steps I'm getting ( boot ) locked OEM or ( vbmeta ) locked OEM
3- I tried to flash recovery alone
4- I tried to flash vbmeta alone
5- I tried to flash both recovery + vbmeta together
The result : FAIL
I think my main problem is unlocking the bootloader using VOL_UP key ..... How to do this while I don't have an option to use VOL_UP key.
even if i'm pressing the VOL_UP key for 1 Minute nothing happens .
you kindness solution will be appreciated

Any chance to have TWRP for F907N?

@ianmacd
First I'd like to say thank you for the work that you've done, and your intro was very well put and super kind to Chris. I know you likely have your hands very full, however I was wondering if you knew of any plans for the F900U or F900U1. I would like to reformat my AT&T phone so that I can get access to unlocking bootloader and hopefully use your TWRP, but I'm not sure if it would work.

[ROM][Android 10][Android 11]Meizu E3 LineageOS 17.1/18.1 ROM Porting (20210418)

{
"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"
}
Hi there,
I prepared an alpha version of LineageOS 17.1/18.1 for Meizu E3 for your taste about it. Now it so more useable as dev-phone for outdoor YouTube viewing. Do play with it your own risk. I am not responsible any liability, nor any technical support too. So please think twice before taking action. AND be safe to backup ALL partitions before and action taken.
You can visit another thread of Meizu E3 unlock bootloader tutorial from your author, to unlock Meizu E3 without any external tool.
Instruction:
(0) to make it align with latest flyme v8000 fw, update system to v8000 is highly recommended. (20200926)
(1) get the phone unlocked bootloader as above mentioned.
(2)download below mentioned fw (boot.img.signed, system.img, vendor.img, recovery.img) in to a folder like "E3_LOS17.1", unzip and get "vendor_image.emmc.win", "system_image.emmc.win" and "boot.img.signed", rename them as boot.img, system.img, recovery.img and vendor.img
(3)hold power+vol_down and do "fastboot.exe boot recovery.img"
(4)in twrp, backup all partition to /sdcard, aka, "/sdcard/system.img", "/sdcard/persist.img"
(5)in host PC backup from phone and upload all above downloaded and unzip rom.img to phone, procedure like open cmd.exe, "mkdir E3", "cd E3/", "adb.exe pull /sdcard .", "adb.exe push E3_LOS17.1 /sdcard"
(6) twrp install, choose install img, select /sdcard/E3_LOS17.1/system.img, system partition, go
(7) twrp install, choose install img, select /sdcard/E3_LOS17.1/vendor.img, vendor partition, go
(8) twrp wipe, choose data partition, go (your data partition got WIPED, all data are LOST)
(9) wait above finish, go back to PC terminal, cmd.exe, issue "adb.exe reboot-bootloader", then "fastboot.exe boot boot.img"
(10) wait for LOS17.1 boots up
optional steps
(2a) you can choose to phh's quack build instead of jasmine_sprout system image as well. download it from phh's github release channel, unpack the zip, use simg->img tool to get regenerated system.ext2.img; check with linux "file" util and get
[email protected]:/mnt/jasmine_vendor# file /mnt/c/d_drive/whyred_temp/los17_20200111_phh_system.img
/mnt/c/d_drive/whyred_temp/los17_20200111_phh_system.img: Linux rev 1.0 ext2 filesystem data, UUID=05050abd-8baa-4dd4-905c-903071f9ac68, volume name "system" (extents) (large files) (huge files)
Click to expand...
Click to collapse
Note:
(1)Please sure to DO backup all the partitions
(2)Please sure DO NOT to flash boot.img to boot partition, every time use fastboot to boot into LOS17.1 thus can easily restore to flyme8 rom
(3)please sure when revert back flyme8, please DO use your own twrp backup to restore all partition is your first choice. Second choise is by flyme8's recovery from recovery partition, or at least the flyme8 recovery downloaded below. DO NOT use TWRP restore the flyme rom directly, and this can avoid many issues; otherwise you are compulsively to reflash flyme once again at least and all your data partition backup become useless; and if you force restore data partition, it wont help, due to internal hw keystore and crypto salt changes. so step (5) "adb.exe pull /sdcard/ ." is essential.
(4)use twrp recovery to restore data partition might not work at all. so once again, backup by using "adb.exe pull /sdcard ." is important. As said, some partition might get changed by bootloader and internal fw, so hw crypto and salt, keystore partition might get changed too after first boot LOS17.1; and you cant backup these partition at twrp screen operation. and even through if you are expert enough, restoring those partitions in adb shell also might not work at all due to same reasoning.
(5)using "adb.exe pull /sdcard ." is important! this is important so as i said 3 times.
(6)backup all partition by "adb shell" if possible. TWRP only list some of usual partition, and some rarely used partition are not listed. Like i suffered from persist partition wiped out and cant restore without a copy. so do a "dd if=/dev/block/bootdevice/by-name/XXX of=/sdcard/XXX" is a good idea.
(7)I had tried my best to make the all mount as "r/o" as possible, but i CANT guarantee all other partition are safe. So best is do as note(6) said.
Release Alpha 13
==================
Latest alpha release on LineageOS 18.1, camera is not working, check below for detail:
Release Alpha 13 · 99degree/android_vendor_meizu_m851q
This release (Alpha 13) is an alpha release that based on brand new Nokia PL2 LineageOS 18.1 release. Detail refer to below: https://lineageos.org/Changelog-25/ This release have an issue about cam...
github.com
Release Beta 2
==================
Latest stable ROM on LineageOS 17.1
Release Beta 2 (20210221) · 99degree/android_vendor_meizu_m851q
This release aimed to get entire system updated to Feb-05 Security bulletin. Changelog: Update to LineageOS Amber 20210214 Known issue: LineageOS clean (wipe data in TWRP) and first time startup wi...
github.com
Older release:
Release note 20210124
==================
Update dts and libmmcamera module. Camera should be alright, actuator is still in progress.
download release 20210126
Release note 20201214
==================
Update to CAF LA.UM.8.2.r2-03400-sdm660.0
Based on LineageOS Nokia PL2 Dragon build 20201208
This is no longer pure CAF due to adreno older fw logic fail.
Selinux enforced now on
Release note 20201011
==================
Update to CAF LA.UM.8.2.r2-02700-sdm660.0
LineageOS Amber 20201011 release, kernel is no longer pure rely on CAF anymore.
It is due to a adreno fw checking logic fail on older fw.
Release note 20200813
==================
Update to CAF LA.UM.8.2.r2-02500-sdm660.0
LineageOS Amber 20200809 release
Release note 20200705
==================
Some sensors are available.
external speaker (TAS2560 SmartAmp) functioning.
Release note 20200701
==================
(1)Special release! Voice-out-loud for social injustice!
(2)Mobile feature enablement
https://github.com/99degree/LineageOS/releases/tag/20200701
Release note 20200613
==================
First version with earphone sound playing. So YouTube is more than possible! This version shifts to official LineageOS.org Yandex Amber build
https://mirrorbits.lineageos.org/full/Amber/20200607/lineage-17.1-20200607-nightly-Amber-signed.zip
Release note 20200303
==================
Workaround the wifi problem, now wifi is working. boot.img.clear is updated.
Release note 20200223
==================
This is a ported version of LineageOS 17.1 based on this thread so you can download the original version of the build over there. In case of preference in phh's treble quack release, it seemed system.img is working well too.
The solo modification in vendor.img included:
(A) fstab.qcom to disable persist partition mount by "r/o", so no longer as "r/w" mode in order to protect it against lost wifi firmware, lost signal, mac address etc.
(B) replace all file lived in /vendor/firmware/* with flyme8's
The modification in system.img:
NIL
Things verified to work:
LCD PANEL
TOUCH PANEL
BLUETOOTH
USB
CHARGING
WIFI
vibration
earphone w/button
mobile feature
speaker and incoming ringing
GNSS
sensors (luminous, proximate, compass, magnet)
selinux-enforced
front camera
back imx362 camera
back imx350 camera(not tested)
Things not working:
those not listed above is considered not working
ROM download:
https://github.com/99degree/android_vendor_meizu_m851q/releases/tag/20210418 for LOS18.1
https://github.com/99degree/android_vendor_meizu_m851q/releases/tag/20210221 for beta 2
release 20210126
release 20201214
https://github.com/99degree/LineageOS/releases/tag/20201011
https://github.com/99degree/LineageOS/releases/tag/20200813 for boot.img and recovery.img
https://github.com/99degree/LineageOS/releases/tag/20200705 system and vendor image
https://github.com/99degree/LineageOS/releases/tag/20200701
https://github.com/99degree/LineageOS/releases/tag/20200613
https://github.com/99degree/LineageOS/releases/tag/20200223
https://github.com/99degree/LineageOS/releases/tag/20200303 for boot.img.clear
Repositories:
https://github.com/99degree/
kernel https://github.com/99degree/android_kernel_meizu_m851q
vendor & release https://github.com/99degree/android_vendor_meizu_m851q
So if you wanted to cook it yourself, please find necessary file with you. All needed files are hosted either in GitHub and LineageOS official Amber/PL2 build),
Please consider to show your support by donation or even YouTube clicks. Last and most importantly, happy ROM flashing and stay away from corona-virus outbreak!
Regards,
99degree

Can you public source code of kernel with device driver? Thank mate

thinhx2 said:
Can you public source code of kernel with device driver? Thank mate
Click to expand...
Click to collapse
Yes, I am on the way to clean up those code. once ready will upload to github and take vlog. Stay tuned.

99degree said:
Yes, I am on the way to clean up those code. once ready will upload to github and take vlog. Stay tuned.
Click to expand...
Click to collapse
Nice sir

99degree said:
...
kernel https://github.com/99degree/android_kernel_meizu_m851q
...
Regards,
99degree
Click to expand...
Click to collapse
How did you manage to port the kernel from code aurora? Any guide or so? I have Santin K1 (almost the same hardware as meizu) Wanna try to port kernel source.

Spencer_D said:
How did you manage to port the kernel from code aurora? Any guide or so? I have Santin K1 (almost the same hardware as meizu) Wanna try to port kernel source.
Click to expand...
Click to collapse
No! Not the way you through. I managed to clone kernel from CAF and search for hardware info. By app "device info hw", google and find some public available driver (basically touch driver and sound driver), add them to CAF tree then analysis the device tree dtb->dts difference. Move them to new dtsi and compile it with kernel as a whole. Then make use of LineageOS Yandex Amber ROM, modify and make it boots into LineageOS, that's it.
So best wish your development on SantinK1.