{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 11 (R), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. 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.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
What's working:
WiFi
RIL (Calls , SMS , Data)
Bluetooth
Fingerprint
Audio
Video
Camera
Camcorder
Flash
IR
FM Radio
Sensors
LED
GPS
VoLTE
VoWiFi
Encryption (FBE)
Known issues:
Wifi Display
Downloads:
Official download page
Instructions:
Upgrade from lineage 17.1: official guide
Fresh Install:
Reboot to recovery
Format /system, /data and /cache
Install LineageOS zip package
Install GApps of your choice [optional]
Reboot
Important note:
Format data is necessary if MIUI was previously installed or device was encrypted with other encryption methods like FBE.
No Custom Kernels are supported in this thread.
Device wiki:
Official wiki link
Device sources:
Device tree source code : https://github.com/LineageOS/android_device_xiaomi_onclite
Kernel source code : https://github.com/LineageOS/android_kernel_xiaomi_onclite
Is this rom compatible with redmi y3?
Hi, can I flash gapps here or na?
by the ways thank you for the good rom, appreciated it!!!
nicoleanns said:
Hi, can I flash gapps here or na?
by the ways thank you for the good rom, appreciated it!!!
Click to expand...
Click to collapse
Yes, you can.
Ahmed.Rajib said:
Is this rom compatible with redmi y3?
Click to expand...
Click to collapse
Yes, the only difference between Redmi Y3 and Redmi 7 is the front camera, and this ROM also has the camera blobs for Y3 front camera.
Hi, GPS doesn´t work for me, I have tried to reinstall ROM but the same problem.
sses43 said:
Hi, GPS doesn´t work for me, I have tried to reinstall ROM but the same problem.
Click to expand...
Click to collapse
What gapps package did you install?
r6680jc said:
What gapps package did you install?
Click to expand...
Click to collapse
This MindTheGapps
sses43 said:
Hi, GPS doesn´t work for me, I have tried to reinstall ROM but the same problem.
Click to expand...
Click to collapse
Use opengapps. Some permission issues are there in other gapps. https://sourceforge.net/projects/opengapps/files/arm64/test/
sses43 said:
This MindTheGapps
Click to expand...
Click to collapse
I used OpenGapps Nano for Android 11 (TEST) and it works fine for me (make sure to download the Nano version for ARM64). Try reflashing the ROM with this Gapps package. (It's labelled "test" but it's stable enough, I'm currently using it)
BTW here are some screenshots
I'm just wondering if I can just upgrade to this by just flashing the zip file with TWRP? Because the steps on how to upgrade from the official guide is only for using adb sideload.
Darth Bidder said:
I'm just wondering if I can just upgrade to this by just flashing the zip file with TWRP? Because the steps on how to upgrade from the official guide is only for using adb sideload.
Click to expand...
Click to collapse
Yes to upgrade from 17.1 to 18.1, just flash the 18.1 zip, then the Android 11 GApps zip and then other zips (Magisk etc.) in TWRP. No wiping or deleting required. I did it this way
which magisk does this rom support? tried 20.4 and it just goes black after redmi logo. tried 21.0 and it reboots to fastboot. any suggestions?
Greekymatrix said:
which magisk does this rom support? tried 20.4 and it just goes black after redmi logo. tried 21.0 and it reboots to fastboot. any suggestions?
Click to expand...
Click to collapse
I used Magisk 21.4 and it seems to be running fine. I first tried the latest version 22.0 but after trying to follow the instructions, I ended up with a bootloop so I had to restore to my backup.
Darth Bidder said:
I used Magisk 21.4 and it seems to be running fine. I first tried the latest version 22.0 but after trying to follow the instructions, I ended up with a bootloop so I had to restore to my backup.
Click to expand...
Click to collapse
Have you tried to flash the 22.0 magisk.apk as a zip file, (rename it to .zip), it worked for me.
aravindCV said:
Have you tried to flash the 22.0 magisk.apk as a zip file, (rename it to .zip), it worked for me.
Click to expand...
Click to collapse
I only tried doing that after it's already doing the bootloops.
First thing I tried was the one stated in the Patching Images instructions. I used the TWRP 3.4 for the Patch a File part which is probably the reason why it failed then I flashed that patched TWRP through fastboot then it started doing the bootloops.
Next time, I'll do that instead,
Darth Bidder said:
I only tried doing that after it's already doing the bootloops.
First thing I tried was the one stated in the Patching Images instructions. I used the TWRP 3.4 for the Patch a File part which is probably the reason why it failed then I flashed that patched TWRP through fastboot then it started doing the bootloops.
Next time, I'll do that instead,
Click to expand...
Click to collapse
I think ,the boot.img of the rom is the one to be patched.That worked for me in lineage 17.1.
I think the patching boot image is the good choice, because we can keep using the lineage recovery. I like it because it's easy to update the rom.
r6680jc said:
Yes, the only difference between Redmi Y3 and Redmi 7 is the front camera, and this ROM also has the camera blobs for Y3 front camera.
Click to expand...
Click to collapse
Thanks bro, I'm new here.
@Dhina_17 Great Works.
Related
No longer supported. but hopefully LoS team can bring Mi 6x back with LOS 20
Code:
[COLOR="Blue"]#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/COLOR]
Detailed installation instructions:
Install LineageOS on Xiaomi Mi 6X
Update to a newer build of the same LineageOS version
Upgrade to a higher version of LineageOS (e.g. lineage-18.1 -> lineage-19.1)
Download link:
LineageOS Downloads
Recommended Google Apps package:
MindTheGapps (choose ARM64 11.0 zip)
Changelog:
Changes for wayne
Bug reports:
How to submit a bug report
LineageOS GitLab
Donate to support development:
Donate via PayPal to LineageOS
XDA:DevDB Information
LineageOS 18.1 for Xiaomi Mi 6X (wayne), ROM for the Xiaomi Mi 6X
Contributors
Source Code: https://github.com/LineageOS
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
ROM Firmware Required: Recommended V12.0.2.0.PDCCNXM
Based On: LineageOS
Version Information
Status: Nightly
Note:
As some users reported, this rom doesn't work with twrp. Please use lineage recovery as mentioned in installation instructions.
Hi @mrmathematica I flashed the ROM using TWRP, and when it finished it rebooted to recovery and got stuck in the TWRP logo. I can flash the LOS recovery, and also one from the LOS unnofficial build, but I can't use the latest TWRP version just like before. Do you know what could have happened and what can I do? Thanks in advance.
Update: the only official TWRP version working for me is 3.3.0.0, which I tried to update and is still stuck in the TWRP logo.
chrisdlc119 said:
Hi @mrmathematica I flashed the ROM using TWRP, and when it finished it rebooted to recovery and got stuck in the TWRP logo. I can flash the LOS recovery, and also one from the LOS unnofficial build, but I can't use the latest TWRP version just like before. Do you know what could have happened and what can I do? Thanks in advance.
Update: the only official TWRP version working for me is 3.3.0.0, which I tried to update and is still stuck in the TWRP logo.
Click to expand...
Click to collapse
https://wiki.lineageos.org/bugreport-howto.html
mrmathematica said:
https://wiki.lineageos.org/bugreport-howto.html
Click to expand...
Click to collapse
I see, I didn't expect this to be a bug. Then, my guess is that the ROM can be flashed using TWRP, right? Thank you
Update: Issue created in GitLab
According to Isaac Chen (our maintainer), he is using 0625 version + twrp (self-compiled from official source), and everything is fine.
My own 6x is fine with either official TWRP 3.3.1 or 3.4.0, but I'm not on Lineage now. So if TWRP 3.4.0 is not working for you at all, I assume the issue is not with this ROM.
mrmathematica said:
According to Isaac Chen (our maintainer), he is using 0625 version + twrp (self-compiled from official source), and everything is fine.
My own 6x is fine with either official TWRP 3.3.1 or 3.4.0, but I'm not on Lineage now. So if TWRP 3.4.0 is not working for you at all, I assume the issue is not with this ROM.
Click to expand...
Click to collapse
I was on AICP before flashing LOS, and latest TWRP was working fine. I reflashed TWRP again and again after this issue but the only version working now in my phone is 3.3.0.0, which is also not working with LOS.
Which ROM are you using? I'd like to try switching to another ROM to see if that fixes this error. I don't know if it's also related to ARB
chrisdlc119 said:
Which ROM are you using? I'd like to try switching to another ROM to see if that fixes this error. I don't know if it's also related to ARB
Click to expand...
Click to collapse
My 6x is on Official Carbon ROM, with official TWRP. Everything works. I recently upgraded to official TWRP 3.4.0 (from 3.3.1, which I used for a long time), and upgrading carbon rom to newer builds always works. As it is the main phone of a family member, I can't easily switch ROM.
mrmathematica said:
My 6x is on Official Carbon ROM, with official TWRP. Everything works. I recently upgraded to official TWRP 3.4.0 (from 3.3.1, which I used for a long time), and upgrading carbon rom to newer builds always works. As it is the main phone of a family member, I can't easily switch ROM.
Click to expand...
Click to collapse
Thanks, I'll try it and will check how is it going
mrmathematica said:
My 6x is on Official Carbon ROM, with official TWRP. Everything works. I recently upgraded to official TWRP 3.4.0 (from 3.3.1, which I used for a long time), and upgrading carbon rom to newer builds always works. As it is the main phone of a family member, I can't easily switch ROM.
Click to expand...
Click to collapse
I had to flash the stock ROM in flashable ZIP to make latest TWRP work again. Now, I'm wondering if I should have not wiped the system partition just before flashing LOS, I ignored most of the ROMs do that by themselves. Also, I just realized the post says recommended firmare is stock 11.X.X. Do you know if the maintainer was using that firmware before flashing LOS or if he just didn't wipe the system partition? The last was my bad, as I said, I ignored that most ROMs wipe system partition during installation.
Thanks in advance.
chrisdlc119 said:
I had to flash the stock ROM in flashable ZIP to make latest TWRP work again. Now, I'm wondering if I should have not wiped the system partition just before flashing LOS, I ignored most of the ROMs do that by themselves. Also, I just realized the post says recommended firmare is stock 11.X.X. Do you know if the maintainer was using that firmware before flashing LOS or if he just didn't wipe the system partition? The last was my bad, as I said, I ignored that most ROMs wipe system partition during installation.
Thanks in advance.
Click to expand...
Click to collapse
See my note in OP: I checked with dev and he think this is an issue with twrp. Lineage recovery as mentioned in instruction is tested to work.
mrmathematica said:
See my note in OP: I checked with dev and he think this is an issue with twrp. Lineage recovery as mentioned in instruction is tested to work.
Click to expand...
Click to collapse
Thanks for following the issue with dev. Now a question would be if by flashing the LOS recovery prior to flashing LOS will allow TWRP to work properly if flashing the recovery later, since in my case I flashed LOS from TWRP, then flashed the LOS recovery and then flashed again LOS to make it boot properly. However, I wasn't able to use latest TWRP until I flashed the latest stock firmware.
Cannot recognize wired headset with type-c interface
Hello, I want to report a problem. The interface of my wired headset is type-c. When I plug in the lineage os and plug in the headset, the device cannot be recognized. When I plug in the headset to play, the sound will come out of the speaker , Can this problem be solved?
Can we apply the lineage recovery using the twrp recovery? Or it has to applied via the adb only? Or has the issue with the TRWP been fixed? Thanks in advance!
Are there any known problems with this ROM?
coolman7 said:
Are there any known problems with this ROM?
Click to expand...
Click to collapse
I don't notice any. If you find any, feel free to report to LineageOS. Or you can mention it here.
OP updated to reflect major version update (from LineageOS 17 to 18).
My China bought Mi 6X is not connecting to Wi-Fi; network is saved but connecting. So decided (have been thinking for some time now) to get rid of the Chinese ROM and unlocked the bootloader. Then I have found out that there is no fastboot ROM for 6X. Luckily I have found this thread. However, I am stuck at "recovery installation" stage.
{
"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"
}
As seen from the screenshot I have tried to flash both LOS Recovery and twrp. Both times when I reboot to recovery MI-Recovery 3.0 is there. What I am doing wrong/incomplete.
nikmgl said:
My China bought Mi 6X is not connecting to Wi-Fi; network is saved but connecting. So decided (have been thinking for some time now) to get rid of the Chinese ROM and unlocked the bootloader. Then I have found out that there is no fastboot ROM for 6X. Luckily I have found this thread. However, I am stuck at "recovery installation" stage.
View attachment 5501929
As seen from the screenshot I have tried to flash both LOS Recovery and twrp. Both times when I reboot to recovery MI-Recovery 3.0 is there. What I am doing wrong/incomplete.
Click to expand...
Click to collapse
I somehow managed to boot to LOS Recovery (trick was pushing the buttons right after flashing). I have followed the sideloading steps for both LOS and GApps carefully, however I am now stuck with LOS Recovery screen saying
E:Emulated failed to bind mount /mnt/staging/emulated/media/0 on /storage/emulated: No such file or directory
Click to expand...
Click to collapse
I have tried rebooting right after sideloading LOS without GApps and same result.
What I am doing wrong/incomplete?
Everything works fine, but sometimes i have random reboots. Also i have no idea how to install only rom firmware recomended at 1-st post, and how can I look currently installed version of the rom firmware?
does anybody know when will lineageos 19 be released for xiaomi mi a2?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Introduction
LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
What's working:
Boot
Bluetooth
Camera / Camcorder
Double Tap to Wake
IR Blaster
RIL (LTE/Dual SIM/SMS)
FM Radio
VoLTE
GPS
WiFi
WiFi Hotspot
USB (ADB/MTP/PTP)
Video Playback
Touch
Sensors
SELinux enforcing
What's not working:
You tell me.
Maybe encryption.
Installation instructions
Download the zip(s).
Install a compatible Recovery, i.e. with vendor support.
Perform a NANDroid backup of your current ROM (Optional)
Wipe data if you come from different ROM. Don't needed if you do an upgrade from LOS 17.1.
Wipe system, cache and vendor partitions.
Flash ROM.
Optional: Install the Google Apps addon package.
Optional: Install Magisk for Root.
Downloads
If you don't have Recovery with vendor support: Unofficial TWRP by nick00007
Rom: https://rolex.yurikoles.com/
Official GApps: Open GApps 10.0 arm64
Latest radio firmware: Xiaomi Firmware Updater by yshalsager
Bonus: I prefer aroma GApps (you choose what to install): Unofficial Open GApps 10.0 arm64 aroma
Thanks To
* AOSP
* Lineage OS Team
* Thago for Triton-kernel
* nick00007 for device and vendor trees, recovery.
XDA:DevDB Information
Lineage OS 17.1 ROM, ROM for the Xiaomi Redmi 4a
Contributors
yurikoles, Thago, nick00007
Source Code: https://github.com/xiaomi-rolex
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: Latest
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: 17.1
Stable Release Date: 2020-06-27
Created 2020-06-27
Last Updated 2020-07-10
Reserved
Changelog:
2020-07-10:
July security patch, r10.0.0_r40.
2020-07-04-2:
June security patch, r10.0.0_r39.
2020-07-04:
Sync from LOS 17.1.
2020-07-01:
Sync from LOS 17.1.
Uploaded a correct recovery to the same dir on my server. Updated OP post accordingly. Thanks to @michal778 for a good bug report.
Added instructions on formatting /data with F2FS for a maximum performance.
2020-06-28:
Sync device and vendor trees from RevengeOS.
Sync from LOS 17.1.
Disable debug during build, so it should be faster now.
2020-06-27:
Initial release.
Reserved
What's the difference from this?
https://forum.xda-developers.com/redmi-4a/development/rom-lineage-os-17-0-unofficial-t3987561
MaxisMan said:
What's the difference from this?
https://forum.xda-developers.com/redmi-4a/development/rom-lineage-os-17-0-unofficial-t3987561
Click to expand...
Click to collapse
My version is shipped with Triton kernel and I hope to provide more frequent updates.
i m using android10 rom with orangefox recovery can i flash directly n the recommended unofficial open gapps size is big can i install official open gapps
Roshan Gangmei said:
i m using android10 rom with orangefox recovery can i flash directly n the recommended unofficial open gapps size is big can i install official open gapps
Click to expand...
Click to collapse
I had updated my post. Any recovery with vendor support or any Android 10 arm64 should work. It's always recommended doing clean flash, e.g. full wipe when you switch between different ROMs. You may still try to do keep your data partition, but please don't report any bugs until you can reproduce them with clean flash.
Do I have a bluetooth connection problem for sound devices?
Any changelog 28/06 from 27/06? Greeting from Russia )
yurikoles said:
My version is shipped with Triton kernel and I hope to provide more frequent updates.
Click to expand...
Click to collapse
Great. :good:
suzver said:
Any changelog 28/06 from 27/06? Greeting from Russia )
Click to expand...
Click to collapse
Greetings from Ukraine, @suzver.
Thanks for reminder, I had added changelog to second post.
Thanks for this awesome ROM,its smooth n fast.everything works perfectly without a glitch.what I did first was changing orangefox recovery to op unofficial twrp via team win apk,without formatting it shows error in twrp n flashing with magisk it did boot up but to twrp again n flash again without it yes it works.I m okay with less customizations.BTW I m using official open gapps nano.Hats off to you.
What you mean by wipe vendor partition"s"?
I understand that I should wipe system, data, cache, dalvik, vendor?
Well, a huge disappointment can't flash lineage-17.1-20200628-UNOFFICIAL-rolex.zip at all. I'm using miui 9.2.6.0 and twrp that you posted. Can't wipe vendor because it's not showing in wipe list, so I'm wiping rest. It's says flashing was successful, but gapps giving error 30 and tells me my android is 7.1.2! Something is wrong. I'm doing clean flash from miui. It's not installing at all, so OS is broken or twrp posted. You tried that twrp?
EDIT: Yup it's twrp thing, i used another that allowed me to wipe vendor, and gapps now flashing. Sir, next time better check please.
WSTxda said:
Do I have a bluetooth connection problem for sound devices?
Click to expand...
Click to collapse
Is this a question? I don't know what you have on your phone. As for me, I didn't check BT audio yet, but I hope to have some BT headset available soon.
michal778 said:
Well, a huge disappointment can't flash lineage-17.1-20200628-UNOFFICIAL-rolex.zip at all. I'm using miui 9.2.6.0 and twrp that you posted. Can't wipe vendor because it's not showing in wipe list, so I'm wiping rest. It's says flashing was successful, but gapps giving error 30 and tells me my android is 7.1.2! Something is wrong. I'm doing clean flash from miui. It's not installing at all, so OS is broken or twrp posted. You tried that twrp?
EDIT: Yup it's twrp thing, i used another that allowed me to wipe vendor, and gapps now flashing. Sir, next time better check please.
Click to expand...
Click to collapse
Thanks for report, @michal778 and sorry for that. I don't remember where I got recovery that I had on my phone. But I found a recommended recovery on 4PDA, I had uploaded it to the same dir on my server and updated OP.
I had double-checked that I get working LOS 17.1 + GApps with it, by flashing MIUI 10.2.3.0 via fastboot first.
Bluetooth work fine with my Redmi AirDots after clean flash lineage-17.1-20200628-UNOFFICIAL-rolex.zip
yurikoles said:
Thanks for report, @michal778 and sorry for that. I don't remember where I got recovery that I had on my phone. But I found a recommended recovery on 4PDA, I had uploaded it to the same dir on my server and updated OP.
I had double-checked that I get working LOS 17.1 + GApps with it, by flashing MIUI 10.2.3.0 via fastboot first.
Click to expand...
Click to collapse
I flashed directly from crdroid 6.7 got some minor issue in twrp as mentioned in my previous post,instead of flashing fastboot miui 10.2.3 can we use minimal firmware of the same(size about41mb) in future.
Sir congratulations for the great ROM! Any chance of this ROM becoming official?
Roshan Gangmei said:
I flashed directly from crdroid 6.7 got some minor issue in twrp as mentioned in my previous post,instead of flashing fastboot miui 10.2.3 can we use minimal firmware of the same(size about41mb) in future.
Click to expand...
Click to collapse
Yes, sure. You may grab one here. I had updated OP, thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community-built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What's working :
Audio
Bluetooth
Camera
EGL
GPS
RIL (Calls, SMS, Data)
Sensors
Video Playback
Wi-Fi
MTP
VoLTE
Everything is Working Except following Bugs
Known issues/Bugs :
Double Tap to Wake
If WiFI Doesnt Work, Try Flashing Custom Kernel
VoWiFi
Selinux is permissive(Temporary. Will soon make it enforcing)
You tell me the rest
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed any root implementation
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless). Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Instructions
Have custom recovery installed
Flash 64Bits Vendor
Download the latest LineageOS Build and GApps(Optional)
Wipe Data
Flash the ROM and GApps(Optional)
Enjoy the rom
Downloads : lineage-17.1-20210319-UNOFFICIAL-olivelite.zip
Credits
LineageOS team
@danascape for much help & Olive trees
@Aghora7
Akira & Joel for help
All Testers& All People Who helped me in a way or Other !
Source Code
ROM: https://github.com/LineageOS
Kernel Source: https://github.com/techyminati/android_kernel_xiaomi_sdm439
If You Liked My Work, Press Thanks On This Thread !
Nice.
Hmm... Why does the telegram groups report bugs that are not mentioned on this Xda tread ? Is the telegram groups misreporting bugs or did you forget to mention those bugs ?
This is awesome!
Will flash, looking to get rid of all the pre-installed apps for a long time now
What is your experience so far? How long is it running for you?
Which recovery do you use for flashing? TWRP standard won't work (error 255), the 64bit versions I found give me a black screen on the olivelite.
Would be happy for some help
Went back to Havoc 3.8 now, the only custom ROM which works fine so far, but GPS is crap (that is my main issue...).
Many thanks in advance!
UltraGOD said:
Which recovery do you use for flashing? TWRP standard won't work (error 255), the 64bit versions I found give me a black screen on the olivelite.
Would be happy for some help
Went back to Havoc 3.8 now, the only custom ROM which works fine so far, but GPS is crap (that is my main issue...).
Many thanks in advance!
Click to expand...
Click to collapse
What about havac 3.7 and 3.8 which is more stable and have less bugs?
Yeah, used the Havoc 3.8. It is faster than the vendor MIUI, but still not what I am looking for.
My major issue is GPS. But I do not know if this is a hardware or software (ROM?) issue.
I'm playing GPS related games, and GPS very often does not match the actual position, plus games running slow on vendor ROM, bit better on Havoc, but still not ideal.
GPS tools like GPS fix or GPS booster only have limited effect...
Also tried some GSI ROMs, but they do not work on the olivelite. Whether the phone crashes when booting or nothing happens at all and it keeps stuck in the "Redmi" boot screen.
Hello,
I'm not good at flashing a rom.
For my phone I use orange fox official recovery and I also tested with TWRP. But when I try to flash the rom I always get a 255 error.
Can anyone help me on what is a 255 error and how not to get it.
to install the recovery I used the commands: fastboot flash recovery.img then I flashed orange-fox with adb sideload
then I tested to put this lineage os.zip on my SD card then flach it put 255 error and I also tested via adb sideload and it did not work
in the instructions to install it says to flach 64Bits Vendor but I'm supposed to find it where?
I'm sorry for my english which can have problems I'm not english and I use a translator (deepl.com)
random user111 said:
Hello,
I'm not good at flashing a rom.
For my phone I use orange fox official recovery and I also tested with TWRP. But when I try to flash the rom I always get a 255 error.
Can anyone help me on what is a 255 error and how not to get it.
to install the recovery I used the commands: fastboot flash recovery.img then I flashed orange-fox with adb sideload
then I tested to put this lineage os.zip on my SD card then flach it put 255 error and I also tested via adb sideload and it did not work
in the instructions to install it says to flach 64Bits Vendor but I'm supposed to find it where?
I'm sorry for my english which can have problems I'm not english and I use a translator (deepl.com)
Click to expand...
Click to collapse
I'm having exactly the same issue
Whether this is not a ROM for the Olivelite or we do something very wrong.
Weird that nobody was able to offer support so far...
The only custom ROM I was able to get to work on the Olivelite is the Havoc 3.8...
Bro can u build 32 bit miui 12 rom...
super rom
Resurrection Remix OS edting plese sir
good rom and good battry backup
Rajvirendra575 said:
good rom and good battry backup
Click to expand...
Click to collapse
Does it run on the Olivelite? If so, which version did you take and how make it work?
UltraGOD said:
Does it run on the Olivelite? If so, which version did you take and how make it work?
Click to expand...
Click to collapse
my devices is redmi 8a olivelite 2gb 32gb rom good ram manengment
Rajvirendra575 said:
my devices is redmi 8a olivelite 2gb 32gb rom good ram manengment
Click to expand...
Click to collapse
Can you tell me what you're using? I canot find a build for the Olivelite. Did you use the GSI? How did you install?
Some short instruction would be great
Same here, please make a small howto - would like to install but dont know how
After try several recoveries - 255 error in all of them.
I install it as images (via fastboot).
I followed this guide to create system.img
How to Extract system.new.dat.br and system.new.dat Files
In this guide, we will show you the steps to extract system.new.dat.br and system.new.dat files which are part of Android custom ROMs.
www.droidwin.com
(in step 5.3 it should by 7 not 1)
I have a bug in this rom with whatsapp. I can not send videos through the application, or upload in the state. It only happens to me with the videos, since the images and other files are sent without problems.
Disclaimer
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Click to expand...
Click to collapse
Hello,
Let me share with you my unofficial Lineage OS 19 build. More informations on the rom on their website.
Don't expect regular updates and full support until the official LOS 19 comes out, as i do it on my free time for my personal use.
Instructions & Prerequisites.
Read documentation before doing anything
adb and fastboot support
Bootloader unlocked
Be on the latest OOS 11 firmware. You can try from a different firmware version but i can't guarantee it will work.
Follow the Lineage 18.1 instructions thread carefully, the instructions work with 19 also
If you need Gapps, check the Gapps guide before doing anything
Root : TRY AT YOUR OWN RISK. You may patch the boot.img from the Google Drive folder with Magisk
Downloads.
ROM : Google Drive (Only the .zip file is needed)
Recovery : Lineage downloads
Check consistent partitions : File
What's working.
At the first boot, statusbar may not work, just reboot the device
You tell me
Sources.
Vendor tree : proprietary_vendor_oneplus
Device trees : android_device_oneplus_instantnoodle
android_device_oneplus_sm8250-common
Hardware tree : android_hardware_oneplus
Kernel tree : android_kernel_oneplus_sm8250
Android version : 12
Security patch level : June, 2022
070522 - A new build is available with Signature Spoofing built-in
Check this out !
{
"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"
}
Credits to @invisibazinga, @OmniTechnaut and @Vega206
reserved too
Sweet Rom. Installed from AICP 16.1 A11 with no problems. Thanks for your work on this!
good evening, does fingerprint and face unlock work with this rom? 5G?
revird9 said:
good evening, does fingerprint and face unlock work with this rom? 5G?
Click to expand...
Click to collapse
Hello,
- Fingerprint works with my 2 thumbs
- Face Unlock isn't baked into the rom (could be a cool challenge to try to add it)
- Preferred network type says "NR/LTE/......", but I can't confirm 5G works as I ain't in town these days
HolyHog said:
Sweet Rom. Installed from AICP 16.1 A11 with no problems. Thanks for your work on this!
Click to expand...
Click to collapse
Thank you and thanks for your feedback !
AICP (A12) is also on my list, I hope I can compile it easily during the next 10 days...
Android 12 or 12.1?
dede3413 said:
Android 12 or 12.1?
Click to expand...
Click to collapse
I assumed you have indian firmware. I'm on the latest global firmware and it stucked on fastboot.
I flashed from IN2023 C.20 (Europe) latest Android 12
keaheng said:
I assumed you have indian firmware. I'm on the latest global firmware and it stucked on fastboot.
Click to expand...
Click to collapse
Neil_Armstrong_ said:
I flashed from IN2023 C.20 (Europe) latest Android
Click to expand...
Click to collapse
i tried C20 and C21 of IN2025 but no luck. Gonna try IN2023. What recovery do you use? the offcial lineage 18.1 recovery or the one on the gdrive?
keaheng said:
i tried C20 and C21 of IN2025 but no luck. Gonna try IN2023. What recovery do you use? the offcial lineage 18.1 recovery or the one on the gdrive?
Click to expand...
Click to collapse
The latest lineage 18.1 recovery
The one on Gdrive doesn't work
Neil_Armstrong_ said:
The latest lineage 18.1 recovery
The one on Gdrive doesn't work
Click to expand...
Click to collapse
You must be on a recovery 12. I extracted the rom with payload dumper and flashed recovery, boot, & dtbo before flashing rom. You always have to at least flash the correct recovery when switching from versions.
Am I able to go from LOS 18 to this?
vanish0104 said:
Am I able to go from LOS 18 to this?
Click to expand...
Click to collapse
Can you ask in the telegram group ? https://t.me/Lineageos_group
I can't tell you with accuracy unfortunately
Neil_Armstrong_ said:
Can you ask in the telegram group ? https://t.me/Lineageos_group
I can't tell you with accuracy unfortunately
Click to expand...
Click to collapse
I was just going to test it myself later tonight. I have backups so I'm not worried. Will update later.
vanish0104 said:
I was just going to test it myself later tonight. I have backups so I'm not worried. Will update later.
Click to expand...
Click to collapse
Update 1: Managed to get it updated from 18.1. Dirty flashing caused a bootoop. Clean flashing will work. I don't know if it would have made a difference in the outcome but I flashed the new recovery before I updated. Gonna try to get it rooted next.
Update 2: Got root. Mission success.
vanish0104 said:
Update 1: Managed to get it updated from 18.1. Dirty flashing caused a bootoop. Clean flashing will work. I don't know if it would have made a difference in the outcome but I flashed the new recovery before I updated. Gonna try to get it rooted next.
Update 2: Got root. Mission success.
Click to expand...
Click to collapse
What recovery did you use and what firmware version?
vanish0104 said:
Update 1: Managed to get it updated from 18.1. Dirty flashing caused a bootoop. Clean flashing will work. I don't know if it would have made a difference in the outcome but I flashed the new recovery before I updated. Gonna try to get it rooted next.
Update 2: Got root. Mission success.
Click to expand...
Click to collapse
Yes it seems Factory Reset is mandatory before flashing another rom (aicp A12 instructions ie)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 13.x (T),
which is designed to increase performance and reliability over stock Android for your device.
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.
Official LineageOS website : https://lineageos.org/
About LineageOS Legal : https://lineageos.org/legal/
Important Information
1. This ROM will never work with any versions of Google Camera (GCam)!
2. You need to flash Stock Android 10 before flashing this ROM.
Downloads Links
LineageOS 20.0:
Official builds: Link
Google Applications (optional):
MindTheGapps: https://wiki.lineageos.org/gapps
Information: Flash the GApps before the first boot. If not, a clean flash is recommended.
Flashing and updating
Please refer to the official installation guide at https://wiki.lineageos.org/devices/akatsuki
Pass SafetyNet
Some apps like banking/payment apps or games require to pass SafetyNet.
1. Download the latest release of ih8sn here.
2. Replace the whole content of system/etc/ih8sn.conf inside the zip file with:
Code:
BUILD_FINGERPRINT=Sony/H8266/H8266:8.0.0/51.1.A.3.159/620448843:user/release-keys
3. Install the zip file through recovery.
Issues and reports
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
Share a log of the error with Logcat for example
Also thanks to:
Olivier
Sjll
The LineageOS Team
The CyanogenMod Team
Everyone involved in working and testing
XDAevDB Information
Lineage 20.0 for Xperia XZ3, ROM for the Xperia XZ3
Contributors
dtrunk90
Source Code: https://github.com/LineageOS
Donation
https://paypal.me/dtrunk90
ROM OS Version: Android 13
ROM Kernel: Linux 4.9
ROM Firmware Required: Official Android 10.0 firmware
Based On: LineageOS
Version Information
Status: Stable
Created 2022-10-23
Last Updated 2022-12-19
Reserved
Speaker bug still existing ?
Chickenboy1703 said:
Speaker bug still existing ?
Click to expand...
Click to collapse
Probably, yes. You've never answered the gitlab issue: https://gitlab.com/LineageOS/issues/android/-/issues/4333
i know its beta but is it sutible for daily use ?
Alex5699 said:
i know its beta but is it sutible for daily use ?
Click to expand...
Click to collapse
I think so, yes. But better wait for the official builds. I won't provide any new builds unless there's a bug which needs to be fixed.
One thing worth noting with this build: the notification LED is way too bright, had to set it below 15% for it to appear like it did before upgrading to 20. When will 20 become official on Sony devices? Monthly updates with the security patch would be nice until it is official.
project_2501 said:
One thing worth noting with this build: the notification LED is way too bright, had to set it below 15% for it to appear like it did before upgrading to 20.
Click to expand...
Click to collapse
Thanks, I'll add this to my TODO list and check if i can reproduce it.
project_2501 said:
When will 20 become official on Sony devices? Monthly updates with the security patch would be nice until it is official.
Click to expand...
Click to collapse
I can't answer that. The LineageOS team is still working hard on 20. No ETAs - that's the rule. ;-) I'll see if I can provide monthly updates, but no promises. You won't get a notification or OTA updates anyway because it's an unofficial build. Unofficial builds need manual updating.
dtrunk90 said:
Probably, yes. You've never answered the gitlab issue: https://gitlab.com/LineageOS/issues/android/-/issues/4333
Click to expand...
Click to collapse
I have tested the changes mentioned for mixer_paths_tavil.xml and the issue still persist.
deleted
Roms works great, except when i flash gapps, its not showing up.
Tried this:
Go to recovery
factory reset
Flash rom (sideload)
Flash gapps (sideload)
reboot.
After reboot, no gapps show up.
Tried mindthegapps and NikGapps
Any tips?
nickholtus said:
Roms works great, except when i flash gapps, its not showing up.
Tried this:
Go to recovery
factory reset
Flash rom (sideload)
Flash gapps (sideload)
reboot.
After reboot, no gapps show up.
Tried mindthegapps and NikGapps
Any tips?
Click to expand...
Click to collapse
Classical A/B device user error. You have to reboot to recovery after flashing rom to switch to the other slot (which is also mentioned in the official install guide @ lineage wiki).
dtrunk90 said:
Classical A/B device user error. You have to reboot to recovery after flashing rom to switch to the other slot (which is also mentioned in the official install guide @ lineage wiki).
Click to expand...
Click to collapse
Forgot to mention, tried that. Actieve slot keeps saying B
i spent 3 days to unlock bootloader in my sony xz3, i tried everything because of that i got weird viruses on my laptop i don't know what to do now i am feeling sad
xxxZero_Twoxxx said:
i spent 3 days to unlock bootloader in my sony xz3, i tried everything because of that i got weird viruses on my laptop i don't know what to do now i am feeling sad
Click to expand...
Click to collapse
You just could have read the official install instructions carefully to avoid that.
I have read all the information! my problem is with bootloader, it says bootloader unlock allowed : No
i have xz3 japanese model sov39
If you can help me with this or if you have any software to bypass or unlock this bootloader I will be grateful !!
xxxZero_Twoxxx said:
If you can help me with this or if you have any software to bypass or unlock this bootloader I will be grateful !!
Click to expand...
Click to collapse
You cannot unlock a bootloader if it says no. And that's also mentioned in the install instructions. And apart from that jp models are not supported in this rom anyways.
Guess I'll have to stick with android 10
& thanks for ur reply !!
xxxZero_Twoxxx said:
Guess I'll have to stick with android 10
& thanks for ur reply !!
Click to expand...
Click to collapse
Months ago, I read about a paid service which chained to be able to turn 'no' to 'yes', but I can't remember their name.