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?
Related
{
"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"
}
Resurrection Remix Oreo
Installation Files
TWRPROM
Open GApps 8.1
Install instructions
(Make sure you have latest Oreo vendor, radio and bootloader)
1. Boot into twrp and wipe data and system.
2. Flash RR ROM zip.
3. Flash TWRP installer zip.
4. Reboot -> recovery (this will reboot you into the other slot).
5. Flash Open Gapps.
6. Reboot and enjoy.
Telegram Group
link
Changelog
Resurrection Remix Github Source
Thanks to @razorloves for the device tree.
Device Source Code: Device Tree
Kernel: Kernel Source
Code:
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.
A lot.
XDA:DevDB Information
Resurrection Remix 6.1.0 for sailfish, ROM for the Google Pixel
Contributors
dylanneve1, razorloves
Source Code: https://github.com/ResurrectionRemix/
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
Based On: LineageOS
Version Information
Status: Stable
Stable Release Date: 2018-08-18
Created 2018-08-18
Last Updated 2018-08-18
Reserved
Battery is draining so quickly ???
@dylanneve1 does it matter which gapps sized package to load or just keep it minimal?
Nvm, read through the XL forum to get the answer
thank you
Keeps crashing into bootloader from recovery. Never seen this before.
August vendor?
DrunkUncas said:
Keeps crashing into bootloader from recovery. Never seen this before.
August vendor?
Click to expand...
Click to collapse
Did you make sure you're on the right slot?
DrunkUncas said:
Keeps crashing into bootloader from recovery. Never seen this before.
August vendor?
Click to expand...
Click to collapse
Pretty sure you need to use July Vendor as August Vendor is targetting Pie and not Oreo...I was able to get it working with July
uodii said:
Pretty sure you need to use July Vendor as August Vendor is targetting Pie and not Oreo...I was able to get it working with July
Click to expand...
Click to collapse
That makes a sense.
How's it running, everyone?
followed the steps for installing this from android P stock since it had microstutters that bothered me but was nothing severe....coming from xiaomi devices i was used to the features available both in the stock rom and in custom roms....the pixel stock rom is sooo basic ...i knew it was vanilla android but i still wasnt prepared for how barebones it was...I needed "my stuff" to be comfortable with it....after flashing RR rom and vendor images....it boots up then restarts like 4 seconds later after displaying the home screen....after rolling back to P the same thing happens...what did i do wrong here?something I overlooked or something?any help would be appreciated this is my main phone still.
pyiedpiper said:
followed the steps for installing this from android P stock since it had microstutters that bothered me but was nothing severe....coming from xiaomi devices i was used to the features available both in the stock rom and in custom roms....the pixel stock rom is sooo basic ...i knew it was vanilla android but i still wasnt prepared for how barebones it was...I needed "my stuff" to be comfortable with it....after flashing RR rom and vendor images....it boots up then restarts like 4 seconds later after displaying the home screen....after rolling back to P the same thing happens...what did i do wrong here?something I overlooked or something?any help would be appreciated this is my main phone still.
Click to expand...
Click to collapse
If you want to flash this you have to first flash the latest oreo factory image so that your phone have the correct bootloader, radio and vendor image.. after flashing factory image just flash the rr rom and reboot into recovery one more time and flash the gapps package . You don't have to flash the vendor image individually. ? Same goes for android P.
Ziauddin_Sameer said:
If you want to flash this you have to first flash the latest oreo factory image so that your phone have the correct bootloader, radio and vendor image.. after flashing factory image just flash the rr rom and reboot into recovery one more time and flash the gapps package . You don't have to flash the vendor image individually. ? Same goes for android P.
Click to expand...
Click to collapse
i did flash the oreo factory image using flash.bat file so i should install RR over this without wiping storage again?sorry first time installing roms on pixels.
pyiedpiper said:
i did flash the oreo factory image using flash.bat file so i should install RR over this without wiping storage again?sorry first time installing roms on pixels.
Click to expand...
Click to collapse
You have to wipe data ,cache and system and then flash rr rom. Storage does not need to be wiped.
Ziauddin_Sameer said:
You have to wipe data ,cache and system and then flash rr rom. Storage does not need to be wiped.
Click to expand...
Click to collapse
Thats what i did,but my device would crash immediately it got to the home screen i flashed the vendor images as well.I managed to install the stock Oreo rom and it doesn't reboot loop anymore....but i cant do playstore app updates or phone ota to P....it shuts down immediately if i try to do so ,requiring me to hold PWR for 30 seconds before its back up again.Sync also causes crash.its possible to flash opengapps on stock rom? since im guessing maybe its outdated play services causing this particular issue.
? September patch please
"Copy your data" in google transfer tool crashes...
Anybody knows how to fix it?
Iis it OK clean flashing this coming from Benzo 9.0 ROM?
@dylanneve1
are you still up to this ?
eurochild said:
@dylanneve1
are you still up to this ?
Click to expand...
Click to collapse
I'm getting my Pixel replaced so I can't do anything now. It should be back in like 8-10 days.
I have sounds problem I'm in stock but all sounds doesn't work call and playing video alo didn't work isearch through XDA found some guys have same issue but I'm asking if i go custom rom Doe's this will fix the problem
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today. We're mainly based on LineageOS so use custom kernels compatible with them!
{
"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:
[SIZE="4"]/*
* 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.
*/[/SIZE]
Features
Click for feature list (helps shorten the OP.)
Always Have a full functional Backup. Just in case!
DOWNLOAD:
ROM -Google Drive
ROM -Sourceforge
TWRP
GAPPS
First time installing crDroid to your Sony Xperia XA2, or coming from another ROM:
** Make sure you're running a proper working Recovery (CWM or TWRP)
1) Copy crDroid zip, gapps zip to your device(sd-card)
2) Boot into Recovery
3) Wipe cache, system, & data (or just cache & system for a dirty flash).
4) Flash ROM
5) Reboot into Recovery again
8) Flash gapps
9) Boot up
For root, AFTER you boot into the ROM, you can go back to recovery and install Magisk XX.x (whatever is most recent).
Upgrading from earlier version of crDroid:
The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.
KNOWN ISSUES
LIST-KNOWN-ISSUES-ON-YOUR-DEVICE-HERE
Don't expect any support if you:
- are not running the included kernel
- have installed any mods such as Xposed!
- have modified system files
Thanks to:
- Google
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
DONATE
(This is link is not for OP. It's for CrDr-team. Ehhh... if u wanna say thx for adoptable rom for your device, just write me in pm, ok? ^.^)
crDroid G+ community
XDA:DevDB Information
[ROM][10.0][UNOFFICIAL]crDroidAndroid v6.3[Pioneer], ROM for the Sony Xperia XA2
Contributors
SGS3_0
Source Code: https://github.com/crdroidandroid
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2019-12-06
Last Updated 2020-03-05
reserved
You should use 50.2.* fw before flashing this rom!
More info here:
https://forum.xda-developers.com/showpost.php?p=78973496&postcount=2
Great Work！
Nice Work, every thing works great
Security patch : 5 December
hi, I want to give this a try.
I come from a clean downgraded XA2 (h3113) from 9 to 8.1, so the bootloader is already unlocked and the phone is rooted with TWRP and Magisk installed. I did the downgrade with Emma tools.
My firmware version is 50.1.A.
Do I have to re-install the Pie 9 update first in order to flash this rom ?
Or can I just flash it and then reboot to recovery, flash the gapps and reboot to recovery and flash the latest firmware from here : https://forum.xda-developers.com/showpost.php?p=78973496&postcount=2
boemien said:
Do I have to re-install the Pie 9 update first in order to flash this rom ?
Click to expand...
Click to collapse
Need Sony firmware ("at least bluetooth, dsp, modem from it") from Pie. As Luk said.
It would be better to update (install) the stock rom (Pie) first.
I have not tested this with Android 8.1-stock. I can not promise the right work and compatibility.
Saint-Gazatus said:
Nice Work, every thing works great for an hour or so, then the UI crash and I need to reboot. I'll try to give you a logcat or some logs (No Gapps, no magisk, no SU)
Security patch : 5 November
Click to expand...
Click to collapse
Ok, do them. I do not observe such problems yet. My phone has been working since the last power-up for more than 122 hours ...
update sources&rebuild
hello ... and many thanks for the work ... understood everything so far but a few days ago an update from crdroid came but unfortunately I don't know anything about mm before recovery and so on ... and had to do everything again on mine Do xa2 sony on it and now the update is gone ... should I just wait until the update comes back or do I have to do something else ???
Chwdp777 said:
hello ... and many thanks for the work ... understood everything so far but a few days ago an update from crdroid came but unfortunately I don't know anything about mm before recovery and so on ... and had to do everything again on mine Do xa2 sony on it and now the update is gone ... should I just wait until the update comes back or do I have to do something else ???
Click to expand...
Click to collapse
chek for updates again?
any new build planned for jan 2020 security patch and 17.1 ?
Saint-Gazatus said:
any new build planned for jan 2020 security patch and 17.1 ?
Click to expand...
Click to collapse
Yes, soon.
Someone can tell me, what is a reason eisting this 3 icons with android logo, if I don`t install anything more than bank app and gouverment app from Google Play? After clean install (3 weeks ago )they doesn`t exist.
https://forum.xda-developers.com/attachment.php?attachmentid=4936249&stc=1&d=1580094543
iHusky said:
Someone can tell me, what is a reason eisting this 3 icons with android logo, if I don`t install anything more than bank app and gouverment app from Google Play? After clean install (3 weeks ago )they doesn`t exist.
https://forum.xda-developers.com/attachment.php?attachmentid=4936249&stc=1&d=1580094543
Click to expand...
Click to collapse
That's pretty normal I think. When I'm first using Android 10's based ROM, it showed up on my phone. After using a few weeks, it was gone. When I tap "App Info", it led me into a google playstore (if you have one) and it literally doesn't show anything.
Hi!
I really like you roms, they add to the XA2. But a question - is there a possibility that you could compile versions without recovery, or with TWRP, instead of the stock one? TWRP is just that much more functional, and now after the flash, i need to reflash the TWRP, and only then carry on with gapps, and the rest..
Just asking, no big deal I'm still VERY grateful for your work!
Rom installed, everything works but the wifi keep switching to my data even if there's connection and signal (with stock firmware there was no problem on this side), other than this: is there any plan to release some updates? On the crdroid site the rom is "unmaintained"
Updated sources and rebuild
Callozz said:
Rom installed, everything works but the wifi keep switching to my data even if there's connection and signal (with stock firmware there was no problem on this side), other than this: is there any plan to release some updates? On the crdroid site the rom is "unmaintained"
Click to expand...
Click to collapse
My PC was broken and I could not compile new versions. Gabriel kicked me from maintainers. I've messaged him in telegram yet. New OTA-updates will be soon.
error when i install ggap
anybody can help me !!!
i Installed the rom successfull but when i started with gapp was not working. the logo is sitl running a long time..
can you help me solve the problem
Dctruc said:
anybody can help me !!!
i Installed the rom successfull but when i started with gapp was not working. the logo is sitl running a long time..
can you help me solve the problem
Click to expand...
Click to collapse
what gapps u installed?
how do u did it?
take a log from boot system for debug.
1)stable gapps here(micro or nano): https://sourceforge.net/projects/opengapps/files/arm64/
2)instal em before system booting! (it's important):
a)boot in twrp
b)install rom
c)reboot twrp again
d)install gapps
e)boot system, done.
{
"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. You can also view the Changelog for a full list of changes & features.
Instructions:
Follow the instructions on the wiki page of your device https://wiki.lineageos.org/devices/#samsung
Note: You may use Odin instead of Heimdall, for this you will need to rename the recovery image to recovery.img and pack it into a tar archive.
Downloads:
Builds: https://download.lineageos.org
GApps: https://wiki.lineageos.org/gapps.html
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Support
Telegram group
Contributors
Linux4, haggertk
Source Code: https://github.com/LineageOS
Kernel source: https://github.com/LineageOS/android_kernel_samsung_gta4xl
reserved
reserved
the golden question:
its possible to came to official build from unofficial without formatting data?
if not. do you plan to continue making builds for the unofficial branch?
flitzjoy said:
the golden question:
its possible to came to official build from unofficial without formatting data?
if not. do you plan to continue making builds for the unofficial branch?
Click to expand...
Click to collapse
Sorry, you can't (as always)
But I will continue unofficial 18.1 builds
Linux4 said:
Sorry, you can't (as always)
But I will continue unofficial 18.1 builds
Click to expand...
Click to collapse
Whats the difference between official and unofficial then? Thanks for your effort btw
AgentZed said:
Whats the difference between official and unofficial then? Thanks for your effort btw
Click to expand...
Click to collapse
Unofficial might less stable because I'll release builds with new stuff that isn't yet merged Into official (I thought that would be a good idea for testing stuff)
Still won't release something completely untested for unofficial tho
wanted to upgrade how it's described on the lineageOS wiki, however I got an error message, followed by being stuck at a "entering fastboot..."-screen.
I will try install stock Rom and repeat install from there.
Edit:
Restarting the process with stock rom helped.
I'm trying the get the first offical nightly build installed and it gets stuck on the blue lineage os loading arch. Anyone else get it to boot to setup? I'm using lineage recovery now. I was going to go back to unofficial and twrp but twrp builds were removed from the twrp thread.
julesism said:
I'm trying the get the first offical nightly build installed and it gets stuck on the blue lineage os loading arch. Anyone else get it to boot to setup? I'm using lineage recovery now. I was going to go back to unofficial and twrp but twrp builds were removed from the twrp thread.
Click to expand...
Click to collapse
Installed yesterday without any problems. I was running the unofficial los prior. Make sure to use the matching los recovery.
Hello,
as the developpement of 17.1 has stopped I'll try in the next days with 18.1. But I have a question:
after wipe in Recovery can I update the LineageOS Recovery than reboot into Recovery and flash the LOS18.1 via LOS Recovery from my external SD-Card and after that Magisk? That's the procedure I did in the past with TRWP but as I never worked with LOS Recovery before (as well as a decrypted internal SD-Card) I wanted first be sure about the procedure.
Is it safe to dirty flash official 18.1 over the unofficial?
Thanks so much for all your hard work on this!
Bracher said:
Hello,
as the developpement of 17.1 has stopped I'll try in the next days with 18.1. But I have a question:
after wipe in Recovery can I update the LineageOS Recovery than reboot into Recovery and flash the LOS18.1 via LOS Recovery from my external SD-Card and after that Magisk? That's the procedure I did in the past with TRWP but as I never worked with LOS Recovery before (as well as a decrypted internal SD-Card) I wanted first be sure about the procedure.
Click to expand...
Click to collapse
Sure, you could also sideload lineage and magisk but external sdcard should work too.
RsConqueror said:
Is it safe to dirty flash official 18.1 over the unofficial?
Thanks so much for all your hard work on this!
Click to expand...
Click to collapse
I already answered this, see this post
Jeez that's embarrassing. I don't know how I missed that.
Sorry I have another urgent question how can I update LOS Recovery (from 17.1 to 18.1)? In TRWP you can change into "install an image" than the recoveries are recognised in LOS Recovery there is no such possibililty you can only flash .zip files no other files are recognised.
Should I transform the image file into a zip file or how do you do that? Sorry I'm only used to TRWP
Bracher said:
Sorry I have another urgent question how can I update LOS Recovery (from 17.1 to 18.1)? In TRWP you can change into "install an image" than the recoveries are recognised in LOS Recovery there is no such possibililty you can only flash .zip files no other files are recognised.
Should I transform the image file into a zip file or how do you do that? Sorry I'm only used to TRWP
Click to expand...
Click to collapse
If you are still on 17.1 recovery you'll have to flash 18.1 recovery with Heimdall/Odin like you did when installing lineage for the first time.
Starting with 18.1 you are also able to flash it via fastbootd in recovery.
Thank you very much for your advice! But after my successfull update to official 18.1 including LOS Recovery I have a new problem, in devellopper modus is no longer the possibilitiy for enlarged reboot, so I can't reboot in recovery. Is this intended and if so why and is there a possibility to circumvent that? All in all I'm not very happy with 18.1 so I'm thinking going back to 17.1 which is unfortunately no longer maintained.
By the way is there a possibility to support your work - at least with some spending? I found no possibility yet
Bracher said:
Thank you very much for your advice! But after my successfull update to official 18.1 including LOS Recovery I have a new problem, in devellopper modus is no longer the possibilitiy for enlarged reboot, so I can't reboot in recovery. Is this intended and if so why and is there a possibility to circumvent that? All in all I'm not very happy with 18.1 so I'm thinking going back to 17.1 which is unfortunately no longer maintained.
Click to expand...
Click to collapse
Advanced reboot setting was moved to System -> Gestures -> Power Menu -> Advanced Restart
Do you have any other problem with 18.1?
Bracher said:
By the way is there a possibility to support your work - at least with some spending? I found no possibility yet
Click to expand...
Click to collapse
There's a paypal link in my profile if that's what you mean, thanks for considering to support me!
Thank you very much - for both information, as I said I suppose I'm getting old (72 year old grandmother...). as for the other problem I'm stuck with Nanodroid it's not possible to flash via Magisk, but that's not a ROM problem it's linked to Nanodroid. Your ROM is fine thanks a lot!!!
{
"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.