[ROM][RMX1971][9.0.0][UNOFFICIAL] LineageOS 16.0 for Realme 5 Pro / Realme Q
- Thread starter thesprintster
- Start date
@thesprintster
Can you fix this in next build?
1st. status bar's height is shorter than the notch's, so it look like this.
2nd. status bar think notch is huge so icons cannot be in pointed area.
Can you fix this in next build?
1st. status bar's height is shorter than the notch's, so it look like this.
2nd. status bar think notch is huge so icons cannot be in pointed area.
Thx fir reply.
I just tried and 1st one is fixed, but the 2nd one is same.
Also changing display to larger is looks weird. Is there any way to both keep display setting and fix this issue?
FW-RMX1971 is the Official Realme's RMX1971EX_11_OTA_0130_all_eKIFcPdqX9wL.ozip FW but without System, Vendor and Boot, I don't know what is the purpose of it but I think maybe it can be for people that mess its internal storage with multiple cROMs or delete things without reason. It could help LOS when people have strange problems.
vbmeta.img. In Android 8 Verified Boot was implemented. Patched vbmeta.img disables Verified Boot.
Is needed for Installing TWRP and custom ROMs.
In some cases when you flash 3rd party code the verified boot refuses to load it and show a message like "(Boot/Recovery) have been Destroyed", so you need flash VBmeta before flash TWRP or before cROM.
You can read more about Android Verified Boot here:
https://source.android.com/security/verifiedboot
https://source.android.com/security/verifiedboot/avb
Rom is smooth, i use this rom some days. It restart so fast.
But, after some days. I can't restart. It stucks in lineage boot animation...
If i di factory reset. Then, i can enter rom again.
What should i do? Is that a bug?
---------- Post added at 04:58 PM ---------- Previous post was at 04:45 PM ----------
So, what's the different between vbmeta and patched vbmeta?
Patched vbmeta allows us to install cROM?
SO? i should flash patched vbmeta before install cROM and twrp?
Where is that packed vbmeta?
But, after some days. I can't restart. It stucks in lineage boot animation...
If i di factory reset. Then, i can enter rom again.
What should i do? Is that a bug?
---------- Post added at 04:58 PM ---------- Previous post was at 04:45 PM ----------
I understand
So, what's the different between vbmeta and patched vbmeta?
Patched vbmeta allows us to install cROM?
SO? i should flash patched vbmeta before install cROM and twrp?
Where is that packed vbmeta?
First of, All Realme's Q and 5pro vbmetas are the same, they don't change between updates too, so it is info that don't change at all although the partitions data change, so I think it must be code signing certificates. It contains plane text that indicate: AVB0, avbtool 1.1.0, vendor, dtbo, boot, recovery and system. That must be the AVB target version and certificates for what partitions.
So, having said that, the patched vmeta is indeed a zeroed file, it only contains the AVB target version (AVB0, avbtool 1.0.0) and nothing else. So is clear that its purpose is bypass the Android Verified Boot to run arbitary code.
You of course can find the zeroed vbmeta in the download section of the OP:
---------- Post added at 12:52 AM ---------- Previous post was at 12:43 AM ----------
I want to add that since LOS have not any Realme's stock FW data in its pacakage it does not update that data too, so FW-RMX1971 seems to be for update the Realme's FW secondary code but without needing to install the Stock FW, therefore preserving the LOS ROM data. Maybe it is for people who have been for a long time on Custom ROM to update that data in his devices.
Increase the size of the zeroed-vbmeta.img
@thesprintster.
I want to do a dumb petition. Can you please increase the zeroed vbmeta.img file to 8,192 bytes to equal the stock?
I mistakenly thinked before that the Realme Q and 5pro has different vbmetas, caused by the different checksum that pruduce my own vbmeta from a TWRP backup. Foolishly I trusted in that, but later seen it again in a hex editor and see that my vbmeta have truncated data caused by the zeroed vbmeta be smaller than the stock.
Maybe it don't do any harm but I think is best practize don't leave traces in that very small file.
@thesprintster.
I want to do a dumb petition. Can you please increase the zeroed vbmeta.img file to 8,192 bytes to equal the stock?
I mistakenly thinked before that the Realme Q and 5pro has different vbmetas, caused by the different checksum that pruduce my own vbmeta from a TWRP backup. Foolishly I trusted in that, but later seen it again in a hex editor and see that my vbmeta have truncated data caused by the zeroed vbmeta be smaller than the stock.
Maybe it don't do any harm but I think is best practize don't leave traces in that very small file.
Attachments
I found 3 files to download:
FW-RMX1971.zip
lineage.zip
vbmeta.img
I'm now confused which one to flash first. Can anyone please help me with the order to flash the files. My bootloader is unlocked and TWRP is ready. I just need to order of flashing to be safe and avoid any bootloops.
Also, when do I flash magisk?
Anyhelp would be greatly appreciated. Thanks!
FW-RMX1971.zip
lineage.zip
vbmeta.img
I'm now confused which one to flash first. Can anyone please help me with the order to flash the files. My bootloader is unlocked and TWRP is ready. I just need to order of flashing to be safe and avoid any bootloops.
Also, when do I flash magisk?
Anyhelp would be greatly appreciated. Thanks!
Last edited:
@thesprintster.
I want to do a dumb petition. Can you please increase the zeroed vbmeta.img file to 8,192 bytes to equal the stock?
I mistakenly thinked before that the Realme Q and 5pro has different vbmetas, caused by the different checksum that pruduce my own vbmeta from a TWRP backup. Foolishly I trusted in that, but later seen it again in a hex editor and see that my vbmeta have truncated data caused by the zeroed vbmeta be smaller than the stock.
Maybe it don't do any harm but I think is best practize don't leave traces in that very small file.
No need to make it so compilcated.
8kb vbmeta is from stock which has enabled android-verification-boot.
The 4kb vbmeta is built from source and has disabled android-verification-boot as required by custom ROM's.
@thesprintster, can you please analyze this logcat?
I pull it while my phone hang on boot animation and 'phone is starting'(or android is starting, i cannot recall correctly).
It also happened twice in crdroid too, but i only pulled this on los16.
First, I thought it was magisk's fault, so i flashed magisk uninstaller but no luck. This bootloop only resolved when I wiped data.
I don't want to suffer with these bootloop anymore.
I pull it while my phone hang on boot animation and 'phone is starting'(or android is starting, i cannot recall correctly).
It also happened twice in crdroid too, but i only pulled this on los16.
First, I thought it was magisk's fault, so i flashed magisk uninstaller but no luck. This bootloop only resolved when I wiped data.
I don't want to suffer with these bootloop anymore.
Last edited:
Thank you sir!
Do I flash everything on TWRP or should I flash vbmeta.img and others via adb fastboot?
Can add support for Exfat file system sdcard? I can't use sdcard that formatted exfat like 128gb
On TWRP you can flash first these:
1. FW-RMX1971.zip
2. lineage.zip
3. Magisk.zip
And then reboot to bootloader/fastboot to flash the disabled vbmeta:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
There's anyone know how to fix multi-touch los or others cusrom, its annoying when playing pubg or moba games.
Im still experiencing this touchscreen issue with ambient display on. What file should I flash?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
14
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
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
Source :
Device tree
Kernel tree
Credits :
@SagarMakhar for his work on Realme X
Thanks to all testers who helped in testing
XDA:DevDB Information
[ROM][RMX1971][9.0.0][UNOFFICIAL] LineageOS 16.0, ROM for the Realme 5 Pro
Contributors
thesprintster, SagarMakhar
Source Code: https://github.com/lineageos
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: TWRP
Based On: Lineage OS
Version Information
Status: Stable
Created 2019-10-18
Last Updated 2019-10-18116New build
New build is now up. link is on OP
Changes:
Switched to custom kernel
Fix install fail for Realme Q users.
Added notch config
Upstream lineage sources5Update
Changes:
Switched to source built vendor
Fixed audio noise during games
Fixed touch delay on boot
Better performance
some minor things more ...
Link in OP
MAKE SURE YOU ARE USING LATEST TWRP!4
