Related
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), 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 LineageOS 15.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
Tips:
SELinux works in permissive enforcing mode
You need at least OxygenOS 5.0 firmware, otherwise you'll get error 7 when installing the zip. Latest firmware is recommended.
Installation:
First time flashing LineageOS 15.1 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery (Latest official TWRP is highly recommended: https://twrp.me/oneplus/oneplusthree.html)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon package
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
ROM OS Version: 8.x Oreo
Version Information
Status: Nightly
Created 2018-01-23
Last Updated 2018-11-16
Frequently Asked Questions
When you're about to ask a question, read the FAQs below, otherwise it'll be ignored.
Rule: NEVER ask for ETA
Q: Can we port treble to our device?
A: NO, unless OnePlus supports treble in official OxygenOS. Treble is trouble, treble is fake news. From my point of view treble brings zero benefit to the device. You already have countless custom ROMs, treble won't bring more fancy ROMs to the device, it just brings endless trouble to device maintainers. The most important point is, some of our proprietary vendor blobs aren't fully decoupled from /system, so fake Treble won't achieve the same effect as Google announced, especially when upgrading to new Android versions via GSIs.
Q: It VoLTE working on our device?
A: I don't know. My carrier doesn't support VoLTE/VoWLAN, but I've added necessary IMS stack to the ROM, and there're actually some users reported working VoLTE. If it doesn't work for you, DON'T issue me, I'm unable to fix it. Notice: If you strongly believe your carrier does support VoLTE/VoWLAN but the toggle doesn't even show up in settings, tell me your carrier's MCC/MNC number (check http://www.mcc-mnc.com/)
Q: Please add support for sRGB/DCI-P3 as cm-14.1
A: Our kernel does support them, you can enable it via sysfs toggle: /sys/class/graphics/fb0/srgb and /sys/class/graphics/fb0/dci_p3, maybe some apps could help you do this easier. The frontend is WIP(in fact it's already under reviewing, will be merged soonDone)
Q: Please add xyz features or fix UI/UX related bugs/regressions
A: All feature requests and UI/UX related stuff should go to LineageOS JIRA: https://jira.lineageos.org, I only take care of hardware-specific stuff.
Q: Can you make my device bypass SafetyNet?
A: https://www.lineageos.org/Safetynet/
So... its start... official?
Yes!!! :victory: Going to try it out once I'm done with work
Nice work! Gonna install it asap and report any issues.
Device OP3T, not rooted, encrypted.
I list here whatever I am able to find:
Charging doesn't make a sound nor vibrate, no matter what settings.
Option to switch hw keys light on/off is missing (i know not real issue, but many prefer them off)
Display modes missing sRGB, DCI-P3
Thank you! Will install and give feedback after few hours.
EDIT:So far so good. Very good for an alpha. But we should wait for official to daily use i think.
Edit again: Official rollout has been started. Except some kernel issues(fixable with custom kernel), great rom. Okay for daily use, no crashes or random reboots. Thanks anyone who put work on it.
Sent from my OnePlus 3 using XDA Labs
twentyfourinc said:
So... its start... official?
Click to expand...
Click to collapse
Nope, not official. Look at Zip name.
After install this build TWRP 3.2.1-0 cannot mount data partition (it's has encrypted) without any error.
good
Another Oreo Rom....
dimon2242 said:
After install this build TWRP 3.2.1-0 cannot mount data partition (it's has encrypted) without any error.
Click to expand...
Click to collapse
I'm wondering if this is the f2fs loopback problem.
Is your data partition f2fs or ext4?
Sent from my OnePlus3T using XDA Labs
valimakik said:
Nice work! Gonna install it asap and report any issues.
Device OP3T, not rooted, encrypted.
I list here whatever I am able to find:
Charging doesn't make a sound nor vibrate, no matter what settings.
Click to expand...
Click to collapse
if you only find this bug, its like beta more than alpha, this is great.
thank you all developers!!
atoyu said:
if you only find this bug, its like beta more than alpha, this is great.
thank you all developers!!
Click to expand...
Click to collapse
So far only that, but i am work atm so i don't have time tinker with everthing.
but it really feels good even at this point.
valimakik said:
So far only that, but i am work atm so i don't have time tinker with everthing.
but it really feels good even at this point.
Click to expand...
Click to collapse
may i know which open gapps you flash??
atoyu said:
may i know which open gapps you flash??
Click to expand...
Click to collapse
Unofficial 8.1 gapps. I used aroma to choose apps that i use.
https://forum.xda-developers.com/redmi-note-3/development/gapps-opengapps-t3720449
Srgb or dci-p3 working?
tashimotor said:
Srgb or dci-p3 working?
Click to expand...
Click to collapse
No, it doesnt have those options atm. And that what is in developer options won't do anything.
Can u try switch it on in kernel auditor app?
tashimotor said:
Can u try switch it on in kernel auditor app?
Click to expand...
Click to collapse
I am not rooted atm, i can check it out later today.
valimakik said:
Unofficial 8.1 gapps. I used aroma to choose apps that i use.
https://forum.xda-developers.com/redmi-note-3/development/gapps-opengapps-t3720449
Click to expand...
Click to collapse
thx for the link, as open gapps didn't list 8.1 for download, can i use 8.0 gapps?
edit: after research , seems somebody have problems when flash 8.0 gapps on 8.1 rom, i try to flash 8.1 gapps.
We predicted that the phone would skip Android 8.0 Oreo and jump straight to Android 8.1 Oreo. The one thing we couldn’t predict is whether or not the update would bring Project Treble compatibility, but we can now confirm that it does. We checked the build.prop file of the release and found ro.treble.enabled was set to true. We haven’t been able to flash a Generic System Image (GSI) to truly test it, but we don’t think that the company would set this property to true if the device isn’t Treble compatible.
Click to expand...
Click to collapse
https://www.xda-developers.com/razer-phone-android-oreo-update-developer-preview/
Fantastic news for the Razer Phone development community! Hopefully with the 8.1 release, we will start seeing ROMs and Kernels coming!
Awesome!!!!!!!!
Lineage here we come!!!!!!!!
MR4 Oreo https://twitter.com/Razer/status/979395268876660736?s=19
Introduction
A spinoff thread from the previously-supported-official thread by Atman.
This thread will contain my unofficial builds for violet. On the 16.0 version, the only real fix (so far...) have been the fingerprint scanner sepolicy denials. I aim to do monthly/bimonthly builds to keep up to date with security patches, as so far I haven't encountered any other issues (let me know).
On the 17.1 version, I have slowly figured out how to make it work, but it is highly experimental.
The 16.0 ROM is stable (I use it as my daily driver).
If you find any bugs, please do take screenshots, give a way for me to replicate it on my device, and send a logcat. If you're super smart, use a logcat and filter for the keyword so I don't have to do even more digging
Please don't tell me to use PE/Mokee commits.
Yet another update. I've got 17.1 builds working without having to resort to cheap tricks and commits (sort of).
Flash instructions
Same as usual:
Reboot to fastboot and flash recovery with fastboot (You have to use the TWRP linked below. Other versions likely won't boot.)
Reboot to recovery TWRP
Wipe to format data, wipe again to wipe system and cache (not necessary if you're updating, only if you're switching ROMs)
Flash firmware (ADB sideload) (this step is dated. The newer builds have a higher target firmware so you should try to flash without the firmware first, then flash the firmware if the ROM doesn't work.)
Flash the ROM (sideload)
Flash GApps, Magisk, etc. as necessary
Done
Downloads (16.0) (STABLE)
Firmware (Dated firwmare)
Recovery (TWRP)
11-Jun-2021 build (with 05-May-2021 security patch), and MD5 Digest
For previous builds see below
Downloads (17.1)
Here's the 17.1 ROM. Here's the md5 hash. It has the March security patch.
It currently does not boot. If you would like to try and help with development, flash the ROM, and then flash the Chinese Q firmware on top of it (this can be downloaded from xiaomifirmwareupdater). Be warned that there is a risk that the newest android keymaster may re-encrypt your device, which in the worst case may require you to format data and/or reflash recovery and/or flash a fastboot MIUI rom. So, it's a bit risky, but likely won't be an issue.
Credits, Sources, etc.
Too many to mention. Atman Shah for getting this device supported earlier last year. ThE_MarD (Marc Bougoin) for other help. Various other names I've seen - Bruno Martins, Weikai Kong, Wang Han... all of the Lineage dev team. I'm sure I'm missing many people who have been involved in the project. I am new, and very much a latecomer to all of this.
Device Tree: https://gitlab.com/mzha/android_device_xiaomi_violet
Kernel Tree: https://gitlab.com/mzha/android_kernel_xiaomi_violet
Other things see my gitlab: https://gitlab.com/mzha
A telegram group to discuss development for 16.0/17.1: t.me/lineageos_violet
Previous builds
07-Nov-2020 (incl. Oct-2020 security patch), with 07-Nov-2020 MD5 Hash
13-Jul-2020 (incl. Jul-2020 security patch), with 13-Jul-2020 MD5 Hash
11-May-2020 (incl. May-2020 security patch), with 11-May-2020 MD5 Hash
Good to see some devs showing interest on this os
will you be adding any customisation? or does it continue as pure lineage os?
e2vinay said:
Good to see some devs showing interest on this os
will you be adding any customisation? or does it continue as pure lineage os?
Click to expand...
Click to collapse
Pure LineageOS. There's more than enough customised ROMs for violet already in my opinion... and I also don't have that much time
hcnulma said:
Pure LineageOS. There's more than enough customised ROMs for violet already in my opinion... and I also don't have that much time
Click to expand...
Click to collapse
That's great
by any chance will you consider adding signature spoofing support? that would be really great. it would help many users go for microG instead of gapps
I completely understand you're starter.
great work. good luck.
Thank you
e2vinay said:
will you consider adding signature spoofing support?
Click to expand...
Click to collapse
No, but there are a few alternatives:
Merge the changes from this RFC and build it
Download the spoofer from https://download.lineage.microg.org/violet/, or get the (ed)Xposed module, or other possibilities...
Will be official Lineage Os?
Can we expect los 17 soon?
himanshu fulmali said:
Can we expect los 17 soon?
Click to expand...
Click to collapse
As per OP: I'm waiting on both Android 10 firmware blobs + kernel to be released by Xiaomi... I'm not sure how the other ROM devs get around this, if it's easy to forward-port or not. But for now, only LOS 16.
Heyyo @hcnulma good to see you got your thread up and going!
As for 17.1? You can work with your current kernel and cherry-pick the fixes that other maintainers of violet are using and same for the device tree and vendor blobs.
As an example, LeEco msm8996 devives are using kernel source code from Marshmallow just rebased on a CAF Q Tag for our kernel since we never got anything newer...
Even once Xiaomi release their kernel source code for Android 10? It would probably take quite a bit of work to shave it down to what you specifically need and then importing it on top of a fresh CAF tag for the kernel or even more work to try and inplement it into uour current kernel.
To get official builds of LOS 16.0 going again for violet you would need to show that you are capable of fixing any major bugs that arise as well.
https://wiki.lineageos.org/submitting_device.html
anywho, hope this information helps bud!
hcnulma said:
As per OP: I'm waiting on both Android 10 firmware blobs + kernel to be released by Xiaomi... I'm not sure how the other ROM devs get around this, if it's easy to forward-port or not. But for now, only LOS 16.
Click to expand...
Click to collapse
I am pretty sure you can use the pixel experience device tree and kernel to compile the ROM just like every other rom
Thank you. If he is stable enough I will use it to build RR PIE
Zjh0094 said:
Thank you. If he is stable enough I will use it to build RR PIE
Click to expand...
Click to collapse
It's definitely stable...
prajwal2001 said:
I am pretty sure you can use the pixel experience device tree and kernel to compile the ROM just like every other rom
Click to expand...
Click to collapse
From what I understand, using their kernel tree will mean I'll have to change a lot of references in my own device tree, and using their device tree on top of that is essentially just building PE, not Lineage.
In any case, I did find the Snapdragon 675 (ie sm6150) kernel trees for Q in several places, https://github.com/sm6150-dev/android_kernel_xiaomi_sm6150 and https://github.com/PixelExperience-Devices/kernel_xiaomi_sm6150. I'll take a closer look into this...
I did find the most recent CAF kernel under sm6150 here, but there seems to be an issue of this not showing up in /quic/la... Something will be resolved. Hopefully.
Request to create group for discussion in Telegram
hcnulma said:
It's definitely stable...
From what I understand, using their kernel tree will mean I'll have to change a lot of references in my own device tree, and using their device tree on top of that is essentially just building PE, not Lineage.
In any case, I did find the Snapdragon 675 (ie sm6150) kernel trees for Q in several places, https://github.com/sm6150-dev/android_kernel_xiaomi_sm6150 and https://github.com/PixelExperience-Devices/kernel_xiaomi_sm6150. I'll take a closer look into this...
I did find the most recent CAF kernel under sm6150 here, but there seems to be an issue of this not showing up in /quic/la... Something will be resolved. Hopefully.
Click to expand...
Click to collapse
you won't have to make any changes in the kernel as far as I know and as for the device tree you just have to make some changes according to the ROM
as every ROM uses the same device tree
and you won't be making pe instead of lineage as the same device tree and kernel are used in every Q ROM except EvoX which uses crimson kernel
hcnulma said:
It's definitely stable...
Click to expand...
Click to collapse
Thanks. I will use it as my benchmark to build RR pie.
---------- Post added 15th February 2020 at 12:03 AM ---------- Previous post was 14th February 2020 at 11:57 PM ----------
hcnulma said:
In any case, I did find the Snapdragon 675 (ie sm6150) kernel trees for Q in several places, https://github.com/sm6150-dev/android_kernel_xiaomi_sm6150 and https://github.com/PixelExperience-Devices/kernel_xiaomi_sm6150. I'll take a closer look into this...
I did find the most recent CAF kernel under sm6150 here, but there seems to be an issue of this not showing up in /quic/la... Something will be resolved. Hopefully.
Click to expand...
Click to collapse
/quick/la/msm-4.14
prajwal2001 said:
you won't have to make any changes in the kernel as far as I know and as for the device tree you just have to make some changes according to the ROM
Click to expand...
Click to collapse
It is precisely the device tree that I'm worried about. From experience, PE has a lot of platform-specific stuff that Lineage doesn't (and the same the other way), and also from trying to figure out the fix to 16.0 I realised there's a lot of context/definition differences between the two device trees. I'd still give it a look, but I suspect it might be easier to just modify the current 16.0 device tree.
RupeshRN said:
Request to create group for discussion in Telegram
Click to expand...
Click to collapse
https://t.me/lineageos_violet.
Zjh0094 said:
/quick/la/msm-4.14
Click to expand...
Click to collapse
Yeah I already figured it was msm-4.14. Have already cloned it but am also considering cherrypicking changes that other devs have done to their kernel trees from 16.0 -> 17.1 as opposed to starting with the CAF kernel. A work in progress.
Sir I'm noob but mokee dev released android 10 and i think mokee and los are pretty same, will he not help you if you contact him?
An update on where I am:
I'm not sure whether to use the PE or Mokee vendor trees. Neither of them have much resemblance to 16.0 tree I have so cherry picking changes will be a nightmare.
The PE vendor tree has a lot of device-tree-specific commits, which will make it a headache to untangle later on. The Mokee vendor tree also has a lot of differing firmware files, though is a bit more similar to the LOS tree.
I'm doing a bit of experimentation to figure out which one will last better in the long run, since I can't seem to get my hands on any MIUI Android Q firmware blobs.
An update on where I am:
I'm not sure whether to use the PE or Mokee vendor trees. Neither of them have much resemblance to 16.0 tree I have so cherry picking changes will be a nightmare.
The PE vendor tree has a lot of device-tree-specific commits, which will make it a headache to untangle later on. The Mokee vendor tree also has a lot of differing firmware files, though is a bit more similar to the LOS tree.
I'm doing a bit of experimentation to figure out which one will last better in the long run, since I can't seem to get my hands on any MIUI Android Q firmware blobs.
Yet another update. I've got 17.1 builds working without having to resort to cheap tricks and commits (sort of).
Here's the 17.1 ROM. Here's the md5 hash. Needless to say, it's very experimental, not stable in the least (expect to get past boot maybe 70% of the time) - I'm getting very mixed results when experimenting myself. Nevertheless, try it out, see what you get. Install it the same way as usual. Keen to get as many eyes on this as possible
LineageOS (Lineage Android Distribution) members or anyone else on this website is 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 the products you find here 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. Your warranty will be void if you tamper with any part of your device / software.
How to Install:
1- Make a backup of your important files
2 - Unlock bootloader with this guide
3 - Flash the TWRP, link here
4 - Move Rom & Gapps (optional) into device storage
5 - Full Wipes
6- Flash Rom & Gapps (gapps are OPTIONAL)
for GAPPS:
Choose Gapps Package ARM64 > 7.1 > Micro and below: visit OpenGAPPS
If during the gapps flash it gives you an error then in the TWRP terminal or on the adb shell you have to execute this command: "mkdir /tmp/bin"
Download:
Releases · XRedCubeX/android_device_meizu_m5c
Contribute to XRedCubeX/android_device_meizu_m5c development by creating an account on GitHub.
github.com
Working:
Boots
Storages
Bluetooth
Wifi
GPS - GNSS
Audio
NOT Working:
Camera
Hotspot
Offline Charging
Special Thanks
LineageOS
Moyster for device trees
Device Tree:https://github.com/XRedCubeX/android_device_meizu_m5c
Vendor Tree: https://github.com/XRedCubeX/android_vendor_meizu_m5c
Assim que possível, irei testar!
Hi Red. I was taking a look at the ROM repository on GitHub, and saw that the default branch is now named cm-13.1. So, are you now working on an Android 6.0 ROM for the M5c?
thiagosousa777 said:
Hi Red. I was taking a look at the ROM repository on GitHub, and saw that the default branch is now named cm-13.1. So, are you now working on an Android 6.0 ROM for the M5c?
Click to expand...
Click to collapse
I have a slight indecision, now I can not carry on the Custom ROM because I do not have the right PC but when I am able to compile it, I will evaluate which one can work better
XRed_CubeX said:
I have a slight indecision, now I can not carry on the Custom ROM because I do not have the right PC but when I am able to compile it, I will evaluate which one can work better
Click to expand...
Click to collapse
I see. I would say that in the long run Lineage 14 would be more worthwhile, since Android 6.0 is becoming outdated, with no support for some apps. But really, I just wanted a ROM to replace Flyme, and its bugs. Also, many of the apps I use don't work, or don't work right on Flyme...
These days I was taking a look at /e/ OS. I've been thinking about venturing into porting this ROM to the M5c. For me it would be a challenge, since I've never done this before. But unfortunately at the moment I also don't have a PC that meets the requirements to compile the ROM
thiagosousa777 said:
I see. I would say that in the long run Lineage 14 would be more worthwhile, since Android 6.0 is becoming outdated, with no support for some apps. But really, I just wanted a ROM to replace Flyme, and its bugs. Also, many of the apps I use don't work, or don't work right on Flyme...
These days I was taking a look at /e/ OS. I've been thinking about venturing into porting this ROM to the M5c. For me it would be a challenge, since I've never done this before. But unfortunately at the moment I also don't have a PC that meets the requirements to compile the ROM
Click to expand...
Click to collapse
I find it useless, just use lineage without gapps and it will be better than /e/, then anyway I don't know where to find the manifest
XRed_CubeX said:
I find it useless, just use lineage without gapps and it will be better than /e/, then anyway I don't know where to find the manifest
Click to expand...
Click to collapse
You are right. However, /e/ has some nice features like e account synchronization, an app store, microG, and some of their apps... Of course we could get that with LineageOS, but it is interesting how /e/ already brings that well integrated and ready.
By the way, I am also looking at other non-Android systems, like Ubuntu Touch...
thiagosousa777 said:
You are right. However, /e/ has some nice features like e account synchronization, an app store, microG, and some of their apps... Of course we could get that with LineageOS, but it is interesting how /e/ already brings that well integrated and ready.
By the way, I am also looking at other non-Android systems, like Ubuntu Touch...
Click to expand...
Click to collapse
Ah beautiful those non-android systems yes, unfortunately we have to forget them because of the prebuilt kernel and unavailable sources
XRed_CubeX said:
Ah beautiful those non-android systems yes, unfortunately we have to forget them because of the prebuilt kernel and unavailable sources
Click to expand...
Click to collapse
Well, from what I've been reading the process is similar to porting LineageOS. You just need the kernel sources and the device specific binary blobs. I'm guessing you know how to get them, don't you?
And the interesting thing is that there is a layer, called Halium, that interacts directly with the hardware. And that is actually what you should port to the desired device. Then you can install any Linux system on top of this layer, like Ubuntu Touch, Plasma Mobile, etc, and these are distributed pre-compiled.
thiagosousa777 said:
Well, from what I've been reading the process is similar to porting LineageOS. You just need the kernel sources and the device specific binary blobs. I'm guessing you know how to get them.
And the interesting thing is that there is a layer, called Halium, that interacts directly with the hardware. And that is actually what you should port to the desired device. Then you can install any Linux system on top of this layer, like Ubuntu Touch, Plasma Mobile, etc, and these are distributed pre-compiled.
Click to expand...
Click to collapse
Mhh ... good, you are informed, however the vendor blobs are bull**** to take, the problem is the kernel sources but Meizu has not released them. However, some time ago I booted a Custom kernel based on ALPS (A custom AOSP from Mediatek to be clear) but the touchscreen doesn't work and I'm looking for a solution around but that I can't find
P.S: Fixing that kernel has great potential, forget android 7, you could also boot android 9 with sources, but as long as they are still working
XRed_CubeX said:
Mhh ... good, you are informed, however the vendor blobs are bull**** to take, the problem is the kernel sources but Meizu has not released them. However, some time ago I booted a Custom kernel based on ALPS (A custom AOSP from Mediatek to be clear) but the touchscreen doesn't work and I'm looking for a solution around but that I can't find
P.S: Fixing that kernel has great potential, forget android 7, you could also boot android 9 with sources, but as long as they are still working
Click to expand...
Click to collapse
I confess I didn't quite understand one thing: so how did you port LineageOS to this device? You didn't need the kernel sources?
thiagosousa777 said:
I confess I didn't quite understand one thing: so how did you port LineageOS to this device? You didn't need the kernel sources?
Click to expand...
Click to collapse
At the time I was doing this lineage, I was with the prebuilt kernel, week ago I had done this kernel port to a twrp and the touch was not working so I left the device alone
XRed_CubeX said:
At the time I was doing this lineage, I was with the prebuilt kernel, week ago I had done this kernel port to a twrp and the touch was not working so I left the device alone
Click to expand...
Click to collapse
Thanks for the clarification! It is a shame that Meizu does this (I wonder if they are not violating the terms of the Linux GPL license by distributing the kernel without publishing the modifications made to the source code).
Anyway, if a solution to this kernel problem related to the touch screen comes up, please let me know. In the meantime I'll keep reading Halium's documentation until a solution comes along, or until I get a compatible phone.
Great work!
Hello. I've been testing this ROM on my M5c and love it. The ROM is very good, fluid, lightweight... the only problem is that the camera doesn't work, as well as the cellular network data. Congratulations for the excellent work.
The ROM will no longer receive bugfixes?
pls compile
publish a release
Hello
I did Bought a Samsung Galaxy Z flip 3 demo version , i want to build TWRP for it
Spoiler: That is Done
yesterday i downloaded the Kernel source code from Samsung , now i just need TWRP Sources and and Create a Device Tree to built it
if you want TWRP for this phone , just comment down below (for some motivation)
Spoiler: that done too , look for the custom working kernel
Now For a The Custom Kernel
I Manage to Get A Custom Kernel Working with A lot Of Optimisations (Thanks @chrisaw and Others) on a Old OneUI (That System That Came with the Kernel) and it work well (it need some minor touches)
the Kernel Cant Work on Newer OneUI and Custom Roms (Pixel EXperience) because Of new Changes in Vendor Are not Compatible with the Kernel
A guess this Need A lot Of Working (Everytime Samsung do it their Way and Dont Care about The Correct Way)
ScreenShot of the Kernel
Spoiler: That is Done too too
now on Focusing on The Custom Rom , i download LineageOS 19.0 Source Code as i will build for 2 separate phones (Galaxy Z Flip3 'snapdragon 888' and UMIDIGI F1 Play 'Mediatek Helio P60') consecutively
this rom will be based on treble gsi patches but working only on Galaxy Z Flip3
i manage to build LineageOS 19.0 for Galaxy Z Flip3 , i will not share it now cause :
1 - it is not daily driver or usable , you can call it pre-alpha
2 - it has a lot of bugs that i saw , it could be other i didn't
3 - it is a Treble gsi just for testing purposes and does not have gapps (gapps needed to be included in the gsi not like a normal rom)
4 - i fix the fingerprint , now it is usable
5 - don't ask me about rear screen , it is perfectly not working at all (if you close the phone , the main display become black , rear screen have just samsung galaxy logo....)
6 - other things i forgot
Any Help will be appreciated
Stay Tune
Thanks
Yeah I'd like to see a fully functional TWRP
yes!
really appreciated!
I'm in
hells yeah
ok so i reinstall my ubuntu setup cause apt went broken , but now im good to start
my initial work is the device tree , it is still WIP
GitHub - shadowofleaf96/android_device_samsung_b2q: For building TWRP for Samsung Galaxy Z Flip 3 5G
For building TWRP for Samsung Galaxy Z Flip 3 5G . Contribute to shadowofleaf96/android_device_samsung_b2q development by creating an account on GitHub.
github.com
the kernel still not building , im working on it
thanks for waiting
GitHub - StarKissed/starkissed-kernel-b2q
Contribute to StarKissed/starkissed-kernel-b2q development by creating an account on GitHub.
github.com
I never finished it, but this may help with getting the kernel to build.
It's based on the ROG Phone 5 changes required for the isolated source.
[SOURCE] ASUS_I005_1-kernel (MacOS / Linux)
WARNING: This is NOT a custom kernel! GPL requires that source is released for Android kernels. It does not, however, require that the source is tracked. https://www.asus.com/supportonly/ROG%20Phone%205%20(ZS673KS)/HelpDesk_Download/ Each...
forum.xda-developers.com
twistedumbrella said:
GitHub - StarKissed/starkissed-kernel-b2q
Contribute to StarKissed/starkissed-kernel-b2q development by creating an account on GitHub.
github.com
I never finished it, but this may help with getting the kernel to build.
It's based on the ROG Phone 5 changes required for the isolated source.
[SOURCE] ASUS_I005_1-kernel (MacOS / Linux)
WARNING: This is NOT a custom kernel! GPL requires that source is released for Android kernels. It does not, however, require that the source is tracked. https://www.asus.com/supportonly/ROG%20Phone%205%20(ZS673KS)/HelpDesk_Download/ Each...
forum.xda-developers.com
Click to expand...
Click to collapse
thanks
samsung released android 12 kernel so i will merge the changes from your kernel to mine
Shadow Of Leaf said:
thanks
samsung released android 12 kernel so i will merge the changes from your kernel to mine
Click to expand...
Click to collapse
That kernel never booted, so that would probably do more harm than good. It does, however, include the changes to make an inline kernel build outside the source. It was more an example than a template.
twistedumbrella said:
That kernel never booted, so that would probably do more harm than good. It does, however, include the changes to make an inline kernel build outside the source. It was more an example than a template.
Click to expand...
Click to collapse
ok
yes that what i will do , i will use the samsung open source kernel (android 12) , fix to boot recovery and boot the system , when it does that i will include your changes and see if it works or not
Thanks for your contribution。
Cyanide_zh said:
Thanks for your contribution。
Click to expand...
Click to collapse
you welcome
some good news
TWRP is Booted on our Galaxy Z Flip 3 (SM-F711B) but touchscreen is not working
i think i have a problem with firmware , stay tuned
Shadow Of Leaf said:
some good news
TWRP is Booted on our Galaxy Z Flip 3 (SM-F711B) but touchscreen is not working
i think i have a problem with firmware , stay tuned View attachment 5671531
Click to expand...
Click to collapse
can you share the non-touch version?
i hope he can find the problem and fix it
Maroshall said:
can you share the non-touch version?
i hope he can find the problem and fix it
Click to expand...
Click to collapse
i think i fix the touchscreen problem and its working
there is some minor problems i will fix them and upload it here
also the kernel does not boot on oneui , i have to fix it
the work is done (or atleast it works)
you can check it here TWRP Thread
@twistedumbrella i build the kernel it works on twrp but no luck with OneUI (even with knox and other security measurements disabled) it does panic (kernel panic) i need to do some investigation regarding this , if you want to help i will upload my kernel source code soon
I have the US version, which is why I abandoned the kernel. I had no way to test the changes specific to Samsung, which would be OneUI.
Your best bet would be looking into the changes for an S21 / S22 because they are going to have the Samsung specific changes.
twistedumbrella said:
I have the US version, which is why I abandoned the kernel. I had no way to test the changes specific to Samsung, which would be OneUI.
Your best bet would be looking into the changes for an S21 / S22 because they are going to have the Samsung specific changes.
Click to expand...
Click to collapse
ah ok thanks
for now i fix to kernel panic , now kernel boot in OneUI But after the loading icon the screens went black
so thanks again and sorry for disturbing you
No worries. I would rather you know I don't know, if that makes sense. Sounds like you are more than capable either way.