• If you are experiencing issues logging in, we moved to a new and more secure software and older account passwords were not able to be migrated. We recommend trying to reset your password, then contacting us if there are issues.
  • Nearly done! Migration cleanup is mostly done. There are a small number of issues left that we continue to work on, but all the heavy lifting is done. We still would love to hear feedback over at this thread and also check out the new XDA app! Thanks and we hope you enjoy the new forums, and thanks for your support of XDA <3

[ROM][RMX1901][9.0.0][UNOFFICIAL] LineageOS 16.0

SagarMakhar

Senior Member
Aug 3, 2016
267
1,898
0
Pune

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 9 (Pie), 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
Pop-up front camera
Audio
Sensors
Flash
GPS
VoLTE


Known issues :
Selinux permissive
Report with logcat if found any

Instructions :
Download the latest build
Reboot to recovery
Make sure you're using stock unmodified vendor.
Wipe data, cache, system ( Don't wipe vendor )
Flash the latest build and GApps
Reboot

Downloads :
Unofficial Builds : Click Here

Credits :
@Art_Chen : for his work on kernel , without that this wouldn't have been possible.
Thanks to all testers who helped in testing

Sources :
Device tree
Common tree

XDA:DevDB Information
Lineage OS, ROM for the Realme X

Contributors
SagarMakhar
Source Code: https://github.com/Art-Chen/android_kernel_realme_sdm710

ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: latest available
Based On: LineageOS

Version Information
Status: Beta

Created 2019-10-07
Last Updated 2019-10-26
 

Dr.Anshuman

Senior Member
Oct 19, 2014
143
67
0
35
Nagpur
im gonna try this ROM and Mokee rom & AEX rom one by one..
Nice to see RMX development is being accelerated by developers.. Thanks Sagar, Samar & Chenxy.
 

adam900710

Senior Member
Dec 20, 2010
86
19
0
The boot.img included can't pass whatever the f**king check realme is doing.

I also tried to flash the boot.img from India version, it doesn't pass either.
So I'm afraid Realme is doing some damn to prevent us from loading the kernel.

But strangely, the recovery from https://forum.xda-developers.com/re...very-unofficial-twrp-realme-x-stable-t3959556 works completely fine.
So I guess there should be a way to pass that check.
 

adam900710

Senior Member
Dec 20, 2010
86
19
0
It looks like even with unlocked bootloader, realme X CN variant is still doing some key verification for boot.img.

Thus if boot.img is not properly signed(?) it won't boot on CN variant, thus CN variant needs a different version of LOS.
Strangely, recovery is not verified at all.

BTW, the official ozip update for CN variant is verifying itself as 1901CN, thus current TWRP won't work properly as it's specifying itself as 1901.
Not a big problem, as the model verification line can be easily removed from update-script, then TWRP can apply the converted zip.
 

mistamikel

Senior Member
Dec 18, 2006
795
82
0
Calgary
It looks like even with unlocked bootloader, realme X CN variant is still doing some key verification for boot.img.

Thus if boot.img is not properly signed(?) it won't boot on CN variant, thus CN variant needs a different version of LOS.
Strangely, recovery is not verified at all.

BTW, the official ozip update for CN variant is verifying itself as 1901CN, thus current TWRP won't work properly as it's specifying itself as 1901.
Not a big problem, as the model verification line can be easily removed from update-script, then TWRP can apply the converted zip.
I'm thinking the same thing.
Anything that I flash with a modded boot.img will not boot (error message)
So I then have to reflash the original boot.img via adb just to be able to boot back into twrp.

The CN version definitely has some extra security in the boot.img, and it's quite disappointing.