Database Develop

[ROM][V][UB][Lollipop][5.1.1][Beta] DirtyUnicorns 9.5 Unofficial [DISCONTINUED]

Dirty Unicorns for Sony Xperia V (LT25i, Tsubasa)​
No longer updated.​
{
"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"
}
#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.
*/
Click to expand...
Click to collapse
Compiled with:
ROM and Kernel: GCC 4.8;
-O3 optimisation
Click to expand...
Click to collapse
Installation:
You need to be on unlocked bootloader!
Always do backup, before updating or installing new ROM.
Click to expand...
Click to collapse
First time flashing, or coming from another ROM
Download ROM
Download GAPPS (Optional)
Flash kernel (boot.img) from the rom zip via fastboot
Boot to recovery
Wipe Data/Factory Reset (wipe Data, Cache, Dalvik-Cache), wipe system
Flash ROM zip
Flash GAPPS zip (Optional)
Reboot
Enjoy!
Click to expand...
Click to collapse
Updating from previous build
Download ROM
Download GAPPS (Optional)
Boot to recovery
Wipe Cache, Dalvik-Cache, wipe system
Flash ROM zip
Flash GAPPS zip (Optional)
Reboot
Enjoy!
Click to expand...
Click to collapse
In case of updating from first build (0505), you MUST flash the kernel from the new release.
Click to expand...
Click to collapse
Known issues:
May have bugs common between all devices with DU and CM (device tree, kernel and proprieraries CM based)
Don't know, you tell me.
Click to expand...
Click to collapse
Downloads:
BasketBuild
AndroidFileHost
Click to expand...
Click to collapse
Gapps:
DU TBO Gapps
TK GAPPS
Click to expand...
Click to collapse
Translation:
Crowdin:
DirtyUnicorns
Click to expand...
Click to collapse
Sources:
Device tree CyanogenMod based.
Sources Dirty Unicorns
Proprietaries TheMuppets proprietary_vendor_sony
Kernel CyanogenMod android_kernel_sony_msm8x60
Click to expand...
Click to collapse
Credits:
Thanks @WhiteNeo for the help with fix not booting TWRP recovery
Thanks @updateing and all contributors, mainteiners
Thanks @z31s1g for awesome Materialised TWRP theme
Dirty Unicorns Team
CyanogenMod Team
Google
Click to expand...
Click to collapse
XDA:DevDB Information
DirtyUnicorns for Xperia V, ROM for the Sony Xperia V
Contributors
ElArchibald
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Version Information
Status: No Longer Updated
Current Beta Version: 9.5
Beta Release Date: 2015-08-05
Created 2015-07-10
Last Updated 2016-07-23

As I promise.. here thread for DirtyUnicorns. Later I'll upload update DU 9.4.

Great work!

I've been using the first build for 2 weeks by now... had just a couple of FCs and I'm very satisfied with it.
Goes down to 0.16% per hour in deep sleep (after 6-7 hrs), but still does around 0.3% during the day when it is being "waked up" more.
The screen time is around 3:10-3:30 in general... but I have seen almost 3:50 on a weekend with almost no calls, no gps but WiFi only for data connection.
Will try the new build!
Thanks for the great job!

First experiences with the new build: DON'T DO A DIRTY FLASH over the first release!
Made the system very laggy. Install only with full wipe (data, system included).
I dirty flashed the first release over the new one, to get back my old system... and got into a bootlop.
So, if you upgrade from the first release, do a FULL WIPE!
Just a couple of thoughts after a couple of hours use...
It is a pretty big upgrade with SlimROM bits.
- Slim PIE is in it and working perfectly
- Slim Recents is in it
- Several other refinements.
- Strangely you can resize navigation bar, but the buttons do not get resized (it worked in the first release).
- Camera DOES NOT WORK (I did not try with other camera apps, but the system included one)
- There are no system sounds.
... so I'm going back to the first release.

stirlitz99 said:
First experiences with the new build: DON'T DO A DIRTY FLASH over the first release!
Made the system very laggy. Install only with full wipe (data, system included).
I dirty flashed the first release over the new one, to get back my old system... and got into a bootlop.
So, if you upgrade from the first release, do a FULL WIPE!
Just a couple of thoughts after a couple of hours use...
It is a pretty big upgrade with SlimROM bits.
- Slim PIE is in it and working perfectly
- Slim Recents is in it
- Several other refinements.
- Strangely you can resize navigation bar, but the buttons do not get resized (it worked in the first release).
- Camera DOES NOT WORK (I did not try with other camera apps, but the system included one)
- There are no system sounds.
... so I'm going back to the first release.
Click to expand...
Click to collapse
Forgot to say "Don't dirty flash new build". It's because first build without -O3 flag and optimizations.
I synced sources.. so new build is uploaded. It's still have Testing status and Beta tag.

Is there a way to edit the drop down toogles for this ROM?

Just let you know that a new build is up. Thanks for the work ElArchibald!
Downloading and testing
Results:
- Still no system sounds
- Camera does not work...
Went back to the first release.

1st build fm not working

Made a try with the 0717 build... well, "nothing" works
- No camera, tried with Camera FV.... does not work either
- No sounds
- FM radio does not work
So got back to the very first 0505 build...

stirlitz99 said:
Made a try with the 0717 build... well, "nothing" works
- No camera, tried with Camera FV.... does not work either
- No sounds
- FM radio does not work
So got back to the very first 0505 build...
Click to expand...
Click to collapse
Please make logcat.

Will do next time.... strangely the very first release (that is not even a release) works very well.

Aaaaaaaaaaaaaaaaaaaaaaah! Sucked everything back! Myyyyyy bad!
You just mentioned the first version's kernel was not optimized... and just got clear to me I did not flash the kernel of the new versions. That is why things were not working.
I'd put this into the first post:
If you upgrade from the very first release (0505), you MUST flash the kernel from the new release.

stirlitz99 said:
Aaaaaaaaaaaaaaaaaaaaaaah! Sucked everything back! Myyyyyy bad!
You just mentioned the first version's kernel was not optimized... and just got clear to me I did not flash the kernel of the new versions. That is why things were not working.
I'd put this into the first post:
If you upgrade from the very first release (0505), you MUST flash the kernel from the new release.
Click to expand...
Click to collapse
Done, info added. Btw new build is up!

Fast report. Still no sounds. :/
Trying to select system sounds (notifications) slows the system.
Does not play music. Apollo FCs on trying to play MP3.
Can someone confirm me?
Will make a logcat later today.

stirlitz99 said:
Fast report. Still no sounds. :/
Trying to select system sounds (notifications) slows the system.
Does not play music. Apollo FCs on trying to play MP3.
Can someone confirm me?
Will make a logcat later today.
Click to expand...
Click to collapse
I think the no sound problem coming from the fm2 apk and libs
Try to delete the FM2 apk after that delete libfmradio.so and libfmradio.sony-iris.so and then u can copy these files from a CM rom for example and replace....
then reboot.

Styxie said:
I think the no sound problem coming from the fm2 apk and libs
Try to delete the FM2 apk after that delete libfmradio.so and libfmradio.sony-iris.so and then u can copy these files from a CM rom for example and replace....
then reboot.
Click to expand...
Click to collapse
Thanks! I just thought to give it a try as I also think it is a "driver" problem.
Strangely, the very first build worked flawless.

Styxie said:
Try to delete the FM2 apk after that delete libfmradio.so and libfmradio.sony-iris.so and then u can copy these files from a CM rom for example and replace....
then reboot.
Click to expand...
Click to collapse
Does not work. :/

[UNOFFICIAL] LineageOS 16.0 for ZTE Axon 7

{
"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"
}
About Lineage OS:
Lin·e·age
/ˈlinēij/
noun
lineal descent from an ancestor; ancestry or pedigree.
a sequence of species each of which is considered to have evolved from its predecessor.
Disclaimer:
LineageOS (Lineage Android Distribution) members or anyone else on this website is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in the products you find here before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Your warranty will be void if you tamper with any part of your device / software.
Warning:
This ROM will not work on devices that have not installed the O bootloader and appropriate modem package below. Also does any build from now on require a vendor partition, by doing this you will lose the ability to flash official builds provided by ZTE. Any failure in this process of flashing or repartitioning could lead to an unrecoverable bricked device.
What's not working:
SELinux is permissive
Instructions:
Attention! The bootloader needs to be unlocked!
Attention! You'll need a vendor partition!
1. Install the Universal bootloader and your model specific modem. Download
2. Flash vendor creation tool. Download (unnecessary, if done already)
* On first flash the device will reboot, just reboot to recovery and reflash the zip.
3. Update your version of TWRP. Download
4. Perform a backup of your current ROM. (optional)
5. Wipe system,data and cache (optional) [Needed if coming from another rom!; always good to avoid bugs]
6. Install the ROM. Download
7. Install GApps. (optional) [Recommended -> Open GApps (arm64) (9.0)]
8. Reboot.
What is CAF?
Code Aurora, a Linux Foundation Collaborative Project, hosts tested open source software code needed to provide upstream enablement for innovative, performance optimized, network connectivity and related ecosystems to support system on a chip (SoC) products. It also serves as a staging area for open source code that is submitted to various upstream projects such as the Linux kernel and Android. CAF also mirrors key upstream projects for use by the community.
Sources, Changes, & Wiki:
Source | Changes | Axon 7 Wiki | Lineage OS
Credits:
@Unjustified Dev
@DrakenFX
XDA:DevDB Information
[UNOFFICIAL] LineageOS 16.0 for ZTE Axon 7, ROM for the ZTE Axon 7
Contributors
OrdenKrieger, Unjustified Dev
Source Code: https://github.com/OrdenKrieger/android_kernel_zte_msm8996
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: O bootloader + region modem
Based On: LineageOS
Version Information
Status: Testing
Created 2018-08-19
Last Updated 2019-07-28

Some features of LineageOS are missing, but they will be merged in future builds.
Some features may or may not work, sometimes also differently. Feel free to ask
any question.

UwU neat p finally

Nice.But its unclear for me...is gapps inbuild android 9 or we still need gappas package? And we can also use b12 0 bootstack from Nfound,correct?

Predatorhaze said:
Nice.But its unclear for me...is gapps inbuild android 9 or we still need gappas package? And we can also use b12 0 bootstack from Nfound,correct?
Click to expand...
Click to collapse
Read the instructions, they are there for a reason.

OrdenKrieger said:
Read the instructions, they are there for a reason.
Click to expand...
Click to collapse
Los 15 is abandoned I assume?
And 16 besides nfc and volte is functional?
Thanks for contributing.

wow. It is all happening very fast.
Thanks

OrdenKrieger said:
Read the instructions, they are there for a reason.
Click to expand...
Click to collapse
lmao,i did.There is nothing mentioned we can use nfound bootstack and it says Gapps is optionally,it doesnt say gapps is inbuild. So what do you mean with optionally? I just ask this so people are not confused,and i am one of them that is confused. OPS in threads can be a mess,or have things missed that can be important

Predatorhaze said:
lmao,i did.There is nothing mentioned we can use nfound bootstack and it says Gapps is optionally,it doesnt say gapps is inbuild. So what do you mean with optionally? I just ask this so people are not confused,and i am one of them that is confused. OPS in threads can be a mess,or have things missed that can be important.You also say its optional to wipe system data cache if come from other rom,but in fact its REQUIRED to wipe system data if you come from other rom
Click to expand...
Click to collapse
GApps is always optional because some people want them and some don't. If you read carefully, on LOS 15.1 is the same.

I have heard Android Pie got GAPPS inbuild and i believe that because google dont want microg users.So its not true...

Predatorhaze said:
lmao,i did.There is nothing mentioned we can use nfound bootstack and it says Gapps is optionally,it doesnt say gapps is inbuild. So what do you mean with optionally? I just ask this so people are not confused,and i am one of them that is confused. OPS in threads can be a mess,or have things missed that can be important
Click to expand...
Click to collapse
Why should I mention other stuff if I already provide a working bootstack. Why would I give a download link for Gapps and add the the optionally tag, if they would be build in.

thnx @OrdenKrieger and all others involved :good:
Nice build - working smooth, no lag
DT2W ok
Used bitgapps as a starter
At last NO echo and incall volume adjustable
FP working
Hotspot OK
camera pics ok, recording crashes when saving - on both pics and video lag on movement
usb preferences work
afaik there is no way in settings to reverse softkeys so i used mine : https://androidfilehost.com/?fid=3700668719832237510 (be sure to be rooted and mount system/vendor)
Notifications work - on lockscreen and leds ok
EDIT : after testing a bit, definitely more heating and i mean a lot, more cpu load (f.e. as on the PPR1 img )..... could not stabilize temp on cpu 92C ! Only after applying powersave in EXKM...definitely something to look into (only Wifi on, no BT, no specific apps running....only the basic stuff to test your build )
EDIT2 : fast charging way more heat on battery - also battery drain too fast even with no cpu load
Will test further

Has anyone tried recording a video using the camera on a clean flash? Does the camera app freeze or crash?

2000impreza said:
Has anyone tried recording a video using the camera on a clean flash? Does the camera app freeze or crash?
Click to expand...
Click to collapse
yep, tried recording now and crashes when saving. Also lag on movement.

I try to flash but brick.
I download the bootloader and modem and Twrp and install them.
TWRP from OP did not see vendor Partition.
After flashing the Rom, no Twrp booting, no System booting...just fastboot working.

Hellsbend said:
I try to flash but brick.
I download the bootloader and modem and Twrp and install them.
TWRP from OP did not see vendor Partition.
After flashing the Rom, no Twrp booting, no System booting...just fastboot working.
Click to expand...
Click to collapse
So, the OP says "FOR NOW THIS BUILD ONLY WORKS ON DEVICES WITH A VENDOR Partition". Did your device have a vendor partition before flashing this one?

ttkian said:
So, the OP says "FOR NOW THIS BUILD ONLY WORKS ON DEVICES WITH A VENDOR Partition". Did your device have a vendor partition before flashing this one?
Click to expand...
Click to collapse
Yes of course, I was running ray steffs LineageOS 16 Treble bevor

Hellsbend said:
Yes of course, I was running ray steffs LineageOS 16 Treble bevor
Click to expand...
Click to collapse
Hi mate!
You shouldnt have used another BL nor twrp if you were on Nfounds and twrp3.2.18.Just flashed this rom and rebooted would have been fine.
Try to revert back to where you came from, at least flash his twrp3.2.18 and do a restore if you can.

raystef66 said:
Hi mate!
You shouldnt have used another BL nor twrp if you were on Nfounds and twrp3.2.18.Just flashed this rom and rebooted would have been fine.
Try to revert back to where you came from, at least flash his twrp3.2.18 and do a restore if you can.
Click to expand...
Click to collapse
Thank you very much, I am on the other LineageOS again.
Flashing Nfounds Twrp through fastboot, than O Bootstack again and I could restore my backup
Maybe they should point on that in the OP here.
I will try again in a minute and report back.
Thank you again!
---------- Post added at 07:26 PM ---------- Previous post was at 06:35 PM ----------
raystef66 said:
Hi mate!
You shouldnt have used another BL nor twrp if you were on Nfounds and twrp3.2.18.Just flashed this rom and rebooted would have been fine.
Try to revert back to where you came from, at least flash his twrp3.2.18 and do a restore if you can.
Click to expand...
Click to collapse
That work's just fine.
I just tried this new build now, but it's just the same as the build you posted earlier today.
The only difference in this build....
Device information now shows Axon7 U
Same small bugs as in the other LineageOS 16 GSI plus wifi bit bugy
Signature spoofing is broken
Not worth it jet setting it up all new again.
I went back to my backup again.
Thank you again.
Edit
Of course, it's easier to flash because Post 1,2 and 3 are "included" now.
So it's quicker to flash.

Hellsbend said:
Thank you very much, I am on the other LineageOS again.
Flashing Nfounds Twrp through fastboot, than O Bootstack again and I could restore my backup
Maybe they should point on that in the OP here.
I will try again in a minute and report back.
Thank you again!
---------- Post added at 07:26 PM ---------- Previous post was at 06:35 PM ----------
That work's just fine.
I just tried this new build now, but it's just the same as the build you posted earlier today.
The only difference in this build....
Device information now shows Axon7 U
Same small bugs as in the other LineageOS 16 GSI plus wifi bit bugy
Signature spoofing is broken
Not worth it jet setting it up all new again.
I went back to my backup again.
Thank you again.
Click to expand...
Click to collapse
Not quite. Mine was derived from Redmi Note 4. It looks the same for sure but devs have done some adjustments as to ECHO, dt2w working, notifications, ....
BUT my LOS16 build had no heating, nice CPU load and no battery drain and no heating when charging at all but had the annoying echo as we know it on other gsi builds and no dt2w, no notifications working on lockscreen, no led...
So there are definitely pros from this build and pros from mine.
Hope they can manage heating.
Also back on AEX as the heating (in my case) was too heavy. Dont want to ruin anything now

[ROM][10.0][UNOFFICIAL]crDroidAndroid v6.3[Pioneer]

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.

[UNOFFICIAL][ROM][A320FL/F/Y] LineageOS 17.x [10.0][64 BIT][Treble]

LineageOS 17.x Unofficial for Galaxy A3 2017​
{
"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 10 (Quack), which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* Your warranty is now void. Or not. Depends.
* It's probably expired anyways :D
*
* 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 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 Gerrit Code Review.​
What's working?
Audio
Calls
Wifi
Hotspot
Mobile data
GPS
Bluetooth
Fingerprint
Camera (both photos and video)
NFC
Sensors
Vibration
Others I have forgot
What isn't working?
Echo present in calls for the other side (no fix currently found)
Video recording with stock camera (fix known, will be implemented in next build)
Encryption and extended storage via SD (possible to fix, didn't have time to debug yet)
Stretched preview in camera, photos are fine (fix has more downsides than upsides)
Supported variants
Galaxy A3 (2017). Dual SIM is also supported.
All variants should be working but only A320FL is well tested since all developers have it.
How to install
Make sure you have latest bootloader and modem before installing this.
Make sure you are using the latest OrangeFox build. (the older ones will fail)
Make sure you have flashed the repartition script.
Download the Lineage build, optionally GApps and Magisk.
In OrangeFox format data. (Menu > Manage Partitions > Data > Format Data)
In OrangeFox wipe everything except SD and OTG.
Flash LineageOS.
Optional: Flash GApps (rightafter).
Optional: Flash Magisk.
Reboot.
Generally it's ok to dirty flash, but if you encounter issues a clean flash should be the first thing on your mind.
Downloads
• ROM
get.mcfy.fr
Google Drive
• Recovery
OrangeFox
• GApps
OpenGApps (arm64): OpenGApps
BiTGApps (arm64): AFH
• Root
Magisk: GitHub
Credits
Huge thanks to:
@Astrako for all the hours spent on the device tree/kernel/vendor/hardware and making this possible.
@McFy for help along the way and letting me use his server as a mirror.
LineageOS Team
Anybody that reported bugs or helped test various stuff, without every one of you Android 10 would never get so stable here
XDA:DevDB Information
[UNOFFICIAL][ROM][A320FL/F/Y] LineageOS 17.x [10.0][64 BIT][Treble], ROM for the Samsung Galaxy A Series 2017 A3, A5, A7
Contributors
MartinYTCZ
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: Latest modem + BL recommended
Version Information
Status: Beta
Created 2020-02-22
Last Updated 2020-08-26

Telegram group
Join here!
Go also thank @Astrako for his work on the DT, kernel, ports, recoveries and many more
Changelogs
- 20200221
Initial build
- 20200403
March security patches
Many optimisations and smaller fixes
Rootdir updated from A6 2018 Q, along with some proprietary files
Graphics now r29, from A6 2018 Q
Way too much stuff to list here, thx @Astrako for the work
- 20200613
Fixed GPlay crashes
June security patch, and all other LineageOS source changes
SEPolicy Enforcing
Reworked shims
Now using new power HAL
Many smaller optimisations
- 20200713
July security patch and all other LineageOS source changes
Reworked overlays
ROM now passes SafetyNet out of the box
Defined location provider to *hopefully* fix location with MicroG
Updated OMX libs
Other smaller fixes and optimisations
- 20200825 20200830
August security patch and all other LineageOS source changes
Updated FP from coral's April patch to keep passing SafetyNet
Switched to proprietary audio HAL - fixed in-call echo
Other smaller fixes and optimisations
NOTE: Encryption is currently extremely broken and your device will not boot if you'll try and encrypt.
- 20210118
January security patch and all other LineageOS source changes
Other smaller fixes and optimisations

Reserved

Nice work, thanks!
Any guess what could cause the SM-320FL to hard reboot when I insert the microSD card, choose to extend the internal memory, then start to format? It rebooted at 20% of the formatting process, then reboots all the time when I give the PIN code after the bootup and it tries to read the microSD card (I guess). If I take out, no reboot of course.
Edit: any temp. workaround? Formatting in twrp or in another device? (For using it as an internal memory extender, not just as an external storage.)

banciii said:
Nice work, thanks!
Any guess what could cause the SM-320FL to hard reboot when I insert the microSD card, choose to extend the internal memory, then start to format? It rebooted at 20% of the formatting process, then reboots all the time when I give the PIN code after the bootup and it tries to read the microSD card (I guess). If I take out, no reboot of course.
Edit: any temp. workaround? Formatting in twrp or in another device? (For using it as an internal memory extender, not just as an external storage.)
Click to expand...
Click to collapse
I'm dumb for not testing this, I gotta look at home

Hello. First nice work !! I used to have your Lineage 16 which worked fine and decided to upgrade to Lineage17. Yet I have some troubles with the camera with the error "unable to connect to the camera" and camera won't launch. When having this error I have spotted that there is a camera icon in the status bar and I can't get rid of it. Else no other problem detected. Thanks.

yann29 said:
Hello. First nice work !! I used to have your Lineage 16 which worked fine and decided to upgrade to Lineage17. Yet I have some troubles with the camera with the error "unable to connect to the camera" and camera won't launch. When having this error I have spotted that there is a camera icon in the status bar and I can't get rid of it. Else no other problem detected. Thanks.
Click to expand...
Click to collapse
I am not the author of Lineage 16.0, I only use the same mirror
The maintainer of LineageOS 16.0 is @McFy.
If you have the problems with the camera, this sounds like an app using the camera when you try to use it and I haven't been able to reproduce the problem. Please check all your apps and report back.
Hope you like the ROM

Ok thanks. Another issue : I can't get split-screen working with any apps. And you?

Other issue : the echos in calls...but well-known issue on lineage. Hope you will find something...

That is good we do have a separate thread of LOS17 now.
Is spoofing (for microG) already included? Not sure whether patcher works for LOS17 already. If one of you guys here get it working with microG - please rise a hand.
Is OrangeFox a must have or can I keep latest TWRP?

starbright_ said:
That is good we do have a separate thread of LOS17 now.
Is spoofing (for microG) already included? Not sure whether patcher works for LOS17 already. If one of you guys here get it working with microG - please rise a hand.
Is OrangeFox a must have or can I keep latest TWRP?
Click to expand...
Click to collapse
From what other users told me spoofing doesn't work with MicroG.
You can either use the TWRP included in the repartition script or latest OrangeFox. Either way it must support /vendor or you'll get error 7 while flashing

MartinYTCZ said:
From what other users told me spoofing doesn't work with MicroG.
You can either use the TWRP included in the repartition script or latest OrangeFox. Either way it must support /vendor or you'll get error 7 while flashing
Click to expand...
Click to collapse
I think you misunderstood this. The Rom is either spoofed (but obviously not, what a pity!) - or it has to be by external tools like Nanodroid Patcher. Otherwise microG will not work. But as I checked that some time ago, the Patcher couldn't handle Android Q. That's why I am asking. So best option (and less effort) would be if ROM is spoofed already.
Vendor I have already with my Treble+GSI LOS 16 Rom.

starbright_ said:
I think you misunderstood this. The Rom is either spoofed (but obviously not, what a pity!) - or it has to be by external tools like Nanodroid Patcher. Otherwise microG will not work. But as I checked that some time ago, the Patcher couldn't handle Android Q. That's why I am asking. So best option (and less effort) would be if ROM is spoofed already.
Vendor I have already with my Treble+GSI LOS 16 Rom.
Click to expand...
Click to collapse
Yup, ROM is not spoofed out of the box, so your only hope is nanodroid patcher, which doesn't seem to work in Q :/
Also if you've already got Treble, you can flash this with the TWRP you are currently using

Hello, thanks for your great job.
I have two points :
- When using your ROM, after UI start, I have the message system_error_manufacturer (msgid="8086872414744210668") popup. I googled and chek the code isBuildConsistent. On my phone, the two checked strings seem ok. So I dont uderstand why I have this message.
- I try to build myself with the gitlab manifest readme. My first atemp was ok but I also have the system_error_manufacturer error message. Some days latter, I try to patch the function with a big /* */ to avoid the check and always return true. I sync the lineage code and patch the isConsistent() function, rebuild and flash my rom. My phone keep on the bootimg anim and never start. On the /proc/last_krnl, nothing else than some SElinux warning. I try with androidboot.selinux=permissive on kernel command line but same result. I delete all my lineage root and resync all from scratch but the build did not boot anymore. Please, could-you check if your build boot with the last comit of lineage 17.1 and android_samsung_universal7870 ?
Thanks by advance.
Pascal.

pascalr0410 said:
Hello, thanks for your great job.
I have two points :
- When using your ROM, after UI start, I have the message system_error_manufacturer (msgid="8086872414744210668") popup. I googled and chek the code isBuildConsistent. On my phone, the two checked strings seem ok. So I dont uderstand why I have this message.
- I try to build myself with the gitlab manifest readme. My first atemp was ok but I also have the system_error_manufacturer error message. Some days latter, I try to patch the function with a big /* */ to avoid the check and always return true. I sync the lineage code and patch the isConsistent() function, rebuild and flash my rom. My phone keep on the bootimg anim and never start. On the /proc/last_krnl, nothing else than some SElinux warning. I try with androidboot.selinux=permissive on kernel command line but same result. I delete all my lineage root and resync all from scratch but the build did not boot anymore. Please, could-you check if your build boot with the last comit of lineage 17.1 and android_samsung_universal7870 ?
Thanks by advance.
Pascal.
Click to expand...
Click to collapse
I am building myself and running the latest at this time (using the crdroid device tree) and everything is running perfectly for me! (even with a few patches of my own like enabling dark mode in defaults app and a few command-line programs like rtl-sdr, no gapps (f-droid only)). Added screenshots to prove it indeed boots.
If I'm not mistaken this ROM uses the android_samsung_universal7870 device tree as it is on Gitlab?
Then the only few bugs I can talk about are the USB settings unable to be changed live while that worked on the outdated device tree from Github (screenshot can be provided), and the Camera, but I know that's already WIP.
(Sure there's echo in calls but... No one was successful at fixing this and even the crappiest patches I tried myself didn't work)
Thanks to all those who works on this device tree.

The provided Rom of the dedicated XDA thread run fine on my device but when building myself, I have the same problem : traped on bootanim.
Strange, I supose it's my buid env, my laptop is on Debian 10 and I did not make any mod on the standard base.
I will try with a VM and Ubuntu LTS as sugested by AOSP Project.

MartinYTCZ said:
LineageOS 17.x Unofficial for Galaxy A3 2017
How to install
Make sure you have latest bootloader and modem before installing this.
Created 2020-02-22
Last Updated 2020-02-22
Click to expand...
Click to collapse
Thank you for great work, can I ask from where can get latest modem and boot-loader without download whole firmware?

Hello,
Problems are solved ?
Echo present in calls for the other side (investigating)
Video recording with stock camera (fix known, will be implemented in next build)
Encryption and extended storage via SD (investigating)
Stretched preview in camera, photos are fine (probably unfixable)
And stay at home.
Best regards

Migrate doesn't detect it as an installed rom, any help?

pascalr0410 said:
Hello, thanks for your great job.
I have two points :
- When using your ROM, after UI start, I have the message system_error_manufacturer (msgid="8086872414744210668") popup. I googled and chek the code isBuildConsistent. On my phone, the two checked strings seem ok. So I dont uderstand why I have this message.
- I try to build myself with the gitlab manifest readme. My first atemp was ok but I also have the system_error_manufacturer error message. Some days latter, I try to patch the function with a big /* */ to avoid the check and always return true. I sync the lineage code and patch the isConsistent() function, rebuild and flash my rom. My phone keep on the bootimg anim and never start. On the /proc/last_krnl, nothing else than some SElinux warning. I try with androidboot.selinux=permissive on kernel command line but same result. I delete all my lineage root and resync all from scratch but the build did not boot anymore. Please, could-you check if your build boot with the last comit of lineage 17.1 and android_samsung_universal7870 ?
Thanks by advance.
Pascal.
Click to expand...
Click to collapse
I have pushed some changes to GitLab yesterday which fix this problem. You should be able to boot a new build just fine now :highfive:

[ROM][10.0][UNOFFICIAL] LineageOS 17.1 [RMX1971] [19/11/2020]

{
"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:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
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.
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.
What's working :
Boots
RIL (Calls, SMS, Data)
Fingerprint
Wi-Fi
Bluetooth
Back camera
Front camera
Audio
Sensors
Flash
GPS
VoLTE
Known issues :
Report with logcat if found any
Instructions :
Download the latest build
Reboot to recovery
Wipe data, cache, system, vendor. (Format Data is recommended)
Flash the latest build and GApps
Reboot
Downloads :
Unofficial Builds : Click here
Source :
Device tree
Kernel tree
Thanks to all testers who helped in testing
XDA:DevDB Information
[ROM][RMX1971][10.0.0][UNOFFICIAL] LineageOS 17.1, ROM for the Realme 5 Pro
Contributors
Bublus,Yog
Source Code: https://github.com/lineageos
ROM OS Version: 10 Q
ROM Kernel: Linux 4.x
ROM Firmware Required: ColorOS
Based On: Lineage OS
Version Information
Status: Stable
Created 2020-04-12
Last Updated 2020-08-3

Updates
1911
19/11Changelog
- Updated security patch
- Added some smoothness tweaks in ui
- All Audio Issues Fixed
- Lineage source upstream
- Improved app opening speed
- Fixed ui shutters
- Added VOOC Charging support
- Some misc improvements
- More fixes and improvements.
1510
15/10 Changelog
- Enforceing Build
- Source Upstream
- Fixed audio delay on audio players
- fixed audio always high on incall
- fixed some other issues with audio
- Kernel Upstreamed to 4.9.237
- Using coral R fp for safetynet
- Several fixes and improvements
- Improved wifi stability/speed
- Updated Radio and CNE blobs from LA.UM.8.6.2.r1-08400-89xx.0
- Added KharaMeParts
- Fixed cast crashing after some time
- Fixed focus not working in camera apps
- Fixed high exposure while trying to scan barcodes in apps like whatsapp, gpay etc
- KCAL Support
- Vibration control inside kharaMeParts
2008
20/08 Changelog
- Enforceing Build (one more step to offical)
- August security patch
- Android-10.0.0_r40 -> android-10.0.0_r41
- Source Upstream
- Built kernel with clang
- Added FM
- Fixed cts failing(U need to enabled magisk hide)
- Updated camera blobs to Q
- Updated audio blobs to Q
- Updated media and audio configs
- Removed unnecessary blobs
- Fixed wifi display crashing
- Kernel upstreamed to 4.9.227
- Several performance improvements & misc changes
- F2FS Support (you can format data and cache to f2fs now)
0308
03/08 changelog:
- Moved to RUI Base
- source upstreams
- Kernel based on Realme 10 Kernel Source
- qcacld-3.0 upstreamed to LA.UM.8.8.r1-07300-SDM710.0
- fw-api upstreamed to LA.UM.8.8.r1-07300-SDM710.0
- qca-wifi-host-cmn upstreamed to LA.UM.8.8.r1-07300-SDM710.0
- Kernel Upstreamed to .226 tag
- Updated some blobs to realemui
- Enabled aosp bluetooth hal v2
- Fixed mic
- July security patch
- Moved audio panel to left side
- Updated Carrier Settings from Coral RPB1.200504.018 6520161
- Updated Blobs to RealmeUI
- Improved app launching speed
- Fixed Random reboot while device kept idle
- Fixed audio crashes and other audio issues
- Updated aptX blobs
- Fixed Vowifi and Vilte(Both should be working fine now)
- Kernel Upstreamed to LA.UM.8.8.r1-07600-SDM710.0
- Builts kernel with clang
- minior bugs fixes
- preformance improved
- Improve dt2w
- overall improments
1704
16/04 change log:
source upstreams
minior bugs fixes
preformance improved
kernel changelog:
Wakelocker is here
overall improments
1805
Update:-
- Sorce side upstream
- Move from android-10.0.0_r33 to android-10.0.0_r35
- Kernel upstream to 4.9.223
- Kernel compiled with Clang 11.0.1
- SELinux Enforcing.
- Updated May coral fingerprint for safety net.
- Fixed mic issues while gaming.

F&Q
1) ROM is bootlooping?
Use the right way to boot it and keep in mind theres 2 variant of Realme 5 Pro
1.RMX1971EX (this one which i test my roms on it)
2.RMX1971 (Q)
both have the same hardware but it not the same software as the some changes in storage,
but both need this steps to boot successfuly on your phone.
Curious_guy said:
From TWRP i followed the steps bellow.
1) Wiped everything
2) Installed C.05 and rebooted to recovery (didnt start on C.05 RUI)
3) Again wiped everything, flashed 20200820 (latest build) and bitgapps(Recommended).
4) Then reboot to system.
Click to expand...
Click to collapse
Thanks for Curious_guy sharing his experiance for the other users to follow
P.S: MAKE SURE U DONT USE OPENGAPPS and use the recommended bitgapps for avoiding anyway of bootlooping until next annoucment
2) What is Unified Realme SDM710 (Realme X,XT,3pro,5pro) Project ?
Unified Realme SDM710 is a project for the SDM710 phones from realme to make it easier for users to get update faster
HOW ?
in an easy way to explin it
its a rom it can be flash and work in [Realme X,XT,3pro,5pro] this way it will be get faster updates for all in the same way.
right now its in beta stage with a booted rom worked for the four roms but there a lot bugs to be fixed before any public release.

installed it so far so good gonna try battery performance and games

Hey, can I flash this ROM after I've updated to Realme UI? Thanks!

sansgood said:
Hey, can I flash this ROM after I've updated to Realme UI? Thanks!
Click to expand...
Click to collapse
no u have to flash coloros first (you dont have to boot it just flashing it will do the job) then flashing this rom

Is fast charging working on this rom I have installed it and installed ampere app to measure it says 3520mA
No clue if its fast charging

whats New
Is there chance of getting official support from lineage os

kemo12533 said:
no u have to flash coloros first (you dont have to boot it just flashing it will do the job) then flashing this rom
Click to expand...
Click to collapse
The fact is, I didn't find any way to downgrade RUI to Color OS. Is there some tutorial for the european version? Big thanks.

sansgood said:
The fact is, I didn't find any way to downgrade RUI to Color OS. Is there some tutorial for the european version? Big thanks.
Click to expand...
Click to collapse
now u can unlock the bootloader u can flash twrp or anyonther recovery then flash coloros

kemo12533 said:
now u can unlock the bootloader u can flash twrp or anyonther recovery then flash coloros
Click to expand...
Click to collapse
I have already my bootloader unlocked and twrp working, but i cant find anywhere to download Color OS firmware for Realme 5 pro. In realme website I can only download the RUI one.

killerhaha100 said:
Is fast charging working on this rom I have installed it and installed ampere app to measure it says 3520mA
No clue if its fast charging
Click to expand...
Click to collapse
As far as out charger is 4 Ampers, I would say yes.

sansgood said:
I have already my bootloader unlocked and twrp working, but i cant find anywhere to download Color OS firmware for Realme 5 pro. In realme website I can only download the RUI one.
Click to expand...
Click to collapse
u can see and download it from here , make sure u select and download RMX1971EX_11_A.17 or earlyer builds

I managed yesterday to downgrade and flash this one and it works like a charm. Very smooth and stable. Thanks for sharing and for the help!

dude this is absolutely great. do you plan releasing updates for this in the future? because it seems like its the first release of 17.1 so there are still a lot of fixes to be done yet by the lineage devs.

sansgood said:
I managed yesterday to downgrade and flash this one and it works like a charm. Very smooth and stable. Thanks for sharing and for the help!
Click to expand...
Click to collapse
Brother,
Can u tell me the procedure to downgrade? now i m in Color OS 7 c02? and is it possible to Realme Ui from custom Rom?

vistaabalaji said:
Brother,
Can u tell me the procedure to downgrade? now i m in Color OS 7 c02? and is it possible to Realme Ui from custom Rom?
Click to expand...
Click to collapse
If you're in Color OS then you have the right firmware and you can flash this rom via TWRP. Make sure you wipe your data and cache before flashing. If you get into recovery after first reboot (could happen if you are in a rom with data encryption), format data and reboot again.

sansgood said:
If you're in Color OS then you have the right firmware and you can flash this rom via TWRP. Make sure you wipe your data and cache before flashing. If you get into recovery after first reboot (could happen if you are in a rom with data encryption), format data and reboot again.
Click to expand...
Click to collapse
sorry, i m in Realme Ui, can you provide me the steps/procedure to downgrade from Realme Ui to Color os 6.

vistaabalaji said:
sorry, i m in Realme Ui, can you provide me the steps/procedure to downgrade from Realme Ui to Color os 6.
Click to expand...
Click to collapse
Yes, of course. This are the steps I followed. I assume you haven't an unlocked bootloader and TWRP installed. If so, you can skip the 3 first steps.
1 - Unlock bootloader following this tutorial. https://c.realme.com/in/post-details/1184734239149522944 . If you face any issue when entering the commands in fastboot mode I would recommend connecting the usb to another port of your computer and try again.
2 - Flash TWRP. You can find a guide here https://forum.xda-developers.com/re...de-newbie-resource-thread-bootloader-t3995285 . It is pretty simple, in summary you must flash the TWRP image and the VBMETA image in fastboot mode.
3 - Enter in TWRP, make a backup of all partitions.
4 - Download ColorOS firmware from here https://realmeupdater.com/downloads/archive/RMX1971EX/ (thanks kemo12533). I downloaded the RMX1971EX_11_A.17 version. You will get an OZIP file that you must copy to your phone. I would recommend copying it to an external SD card.
5 - From TWRP, wipe system, data, cache and dalvik cache. Press install and select the ColorOS ozip you moved to SD.
6 - Press reboot system and you should boot into color OS. If your phone reboots into recovery mode again, format data (keep in mind that this will erase everything in your phone storage).

Thank you very much for your effort. May I ask if this will work with european models? Are there really no known issues in the very first release? Will this be added to the official download lists?