[ROM][11.0.0_r48]LineageOS 18.1 for Realme X2 Pro (RMX1931/CN)[UNOFFICIAL]

[_JoeD_]

Thanks a lot Karthick and other devs. I can confirm the new method 2 works to upgrade to the new version. I've been using it for a day and everything seems to be working fine. Good job!

 

[_JoeD_]

I know it's out of scope for our devs but does anybody know how to root this version? Magisk is not working (even tried cannary). I don't really need root but I need it once to enable diag mode to patch the modem profile to get voWifi working for US T-Mobile.

 

[Karthick Chandran]

I know it's out of scope for our devs but does anybody know how to root this version? Magisk is not working (even tried cannary). I don't really need root but I need it once to enable diag mode to patch the modem profile to get voWifi working for US T-Mobile.

https://xdaforums.com/t/phh-treble-...or-phhusson-source-based-treble-gsis.3811563/

Give this a try

 

[zheka99]

Hello. Thanks for the update.
With the kernel from telegram, my battery is very good again!

Is it possible to set widevine to level 1 in this rom?

Strangely, I still had 2 reboots. Global 12gb

 

[_JoeD_]

https://xdaforums.com/t/phh-treble-...or-phhusson-source-based-treble-gsis.3811563/

Give this a try

Thanks Karthick, unfortunately non of these worked, I also tried an old supersu. Everybody has been using magisk, so nobody updated these packages.. I'm hoping at some point magisk will work again.

 

[Karthick Chandran]

Hello. Thanks for the update.
With the kernel from telegram, my battery is very good again!

Is it possible to set widevine to level 1 in this rom?

Strangely, I still had 2 reboots. Global 12gb

Reboots after flashing that kernel, right?

 

[zheka99]

Reboots after flashing that kernel, right?

Yes.

And DC dimming is off

 

[juanantofb]

Hi DEV, without kernel i do not have eny reboot fine fine fine.

What is the telegran group link?

Regards.

Reboots after flashing that kernel, right?

 

[Karthick Chandran]

Hi DEV, without kernel i do not have eny reboot fine fine fine.

What is the telegran group link?

Regards.

I think xda won't allow me post the link here, you can dm me to get the link

 

[Karthick Chandran]

Yes.

And DC dimming is off

yep, i disabled it to check something

 

[jection]

I know it's out of scope for our devs but does anybody know how to root this version? Magisk is not working (even tried cannary). I don't really need root but I need it once to enable diag mode to patch the modem profile to get voWifi working for US T-Mobile.

You got VoLTE to work on T-Mobile? How?

 

[_JoeD_]

You got VoLTE to work on T-Mobile? How?

Yes, before the latest update. Basically, you need root to enable diag mode (setprop command). Then install snapdragon PST tool and use PDT to change the modern profile. Once i changed to TMO-Commercial and rebooted both voWifi and voLTE worked. Currently we don't have root, so I'm stuck.

 

[_JoeD_]

I'm not sure if I'm the only one but there are 2 things that bother me about the latest update. I see screen flicker when the auto brightness is adjusted, sometimes i get a weird green tint over the whole screen. The other thing i noticed is that Google camera is not able to switch to a different back camera. If I do, the app keeps crashing. It did work fine before the update.

 

[Karthick Chandran]

I'm not sure if I'm the only one but there are 2 things that bother me about the latest update. I see screen flicker when the auto brightness is adjusted, sometimes i get a weird green tint over the whole screen. The other thing i noticed is that Google camera is not able to switch to a different back camera. If I do, the app keeps crashing. It did work fine before the update.

screen flicker will be fixed on next update

it will be also fixed if you flash this kernel https://drive.google.com/uc?id=1bANiviQ4y3kj1IRF35NJWCB2jrsUin0x&export=download

& Google camera aux issues, those don't work even on rui2 stock rom, so it won't work here too

 

[BTW lover]

Just a quick question regarding some fishy behavior of my phone recently:

For some reason it uses several hundreds of MB of mobile data in just a few days, mobile data usage tells me it's system updates doing this. Once I saw this I remembered that I've had some strange popups (two or three times) in the past that told me android was out of date and needs an update 8or something similar, can't remember precisely).

Is it possible the phone is doing something strange for some reason or am I being hacked?

Edit: looking for a picture of the popup on the net I found that others had the same popup, here's a pic

So it seems that it might not be fishy, but now it also seems like this is eating into my mobile data without me being able to disable it again, any ideas?

 

[SimfyLogBot]

Just a quick question regarding some fishy behavior of my phone recently:

For some reason it uses several hundreds of MB of mobile data in just a few days, mobile data usage tells me it's system updates doing this. Once I saw this I remembered that I've had some strange popups (two or three times) in the past that told me android was out of date and needs an update 8or something similar, can't remember precisely).

Is it possible the phone is doing something strange for some reason or am I being hacked?

Edit: looking for a picture of the popup on the net I found that others had the same popup, here's a picView attachment 5531835

So it seems that it might not be fishy, but now it also seems like this is eating into my mobile data without me being able to disable it again, any ideas?

I had the same problem and "fixed" it by installing the newest gapps version. In my case also i have a noticeable battery drain. My uneducated guess this things are related to each other. i am now running the version before the newsest update on Jan 21, 2022.(18.1.20211031) maybe an Update will fix my problem but the update process sadly looks more complicated than a "normal" dirty flash.

 

[quwenfast]

注意，CN版本的RMX1931无法刷入这些ROM，会提示e3004报错；所以我尝试用作者发布的橙狐REC再次刷入；不幸的是，它卡在fastboot了；借着它还能进REC,我把官方otg解压后的zip包刷入手机，虽然提示成功，但是它仍然卡fastboot，结果我尝试用realme 线刷工具线刷otg文件，它仍然提示成功，不过还是无法进入系统，之后它就一直卡在fastboot，recovery也进不去了；得益于我在中国，我免费享受了一次官方的系统维修，不过我又试了一次其他办法，但是又失败了

Google Translation:

Note that the CN version of RMX1931 cannot be flashed into these ROMs, and it will prompt e3004 to report an error; so I try to flash it again with the orange fox REC released by the author; unfortunately, it is stuck in fastboot; I flashed the decompressed zip package of the official otg into the mobile phone. Although the prompt was successful, it still stuck in fastboot. As a result, I tried to use the realme flash tool to flash the otg file. Stuck in fastboot, recovery can't get in; thanks to my being in China, I enjoyed an official system maintenance for free, but I tried other methods again, but failed again

 

[Rogerdave]

Need some guidance or clues from any of you.

Mine is a CN version, everything has gone fine with the latest build at the 1st attempt, and things screwed up after flashing latest Magisk 21.4 ....

Rebooting to system and screen turned black after realme logo, flashing all again with no success.

Tried flashing latest TWRP but screen turned black after splash screen of TWRP when booting to recovery. Switching back to OFox has same problem.

Tried flashing those stock image files (boot.img, system.img, odtb.img and vendor.img) directly at fastboot, screen still turned black when booting to system.

Just tried downloading and flashing OFox and vbmeta files from the post, now the phone is prompted "The current images (boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it." with a red triangle.

I have tried every way I know with no success. Any hint / clue / guidance is much appreciated to save my phone, thank you.

 

[Rogerdave]

Need some guidance or clues from any of you.

Mine is a CN version, everything has gone fine with the latest build at the 1st attempt, and things screwed up after flashing latest Magisk 21.4 ....

Rebooting to system and screen turned black after realme logo, flashing all again with no success.

Tried flashing latest TWRP but screen turned black after splash screen of TWRP when booting to recovery. Switching back to OFox has same problem.

Tried flashing those stock image files (boot.img, system.img, odtb.img and vendor.img) directly at fastboot, screen still turned black when booting to system.

Just tried downloading and flashing OFox and vbmeta files from the post, now the phone is prompted "The current images (boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it." with a red triangle.

I have tried every way I know with no success. Any hint / clue / guidance is much appreciated to save my phone, thank you.

My phone is back on finally, and I may share my experience here as reference. Inspired by the post from genernal section, I have run following erase commands at fastboot to erase everything.

fastboot erase boot
fastboot erase dtbo
fastboot erase recovery
fastboot erase metadata
fastboot erase vbmeta
fastboot erase system
fastboot erase vendor
fastboot erase userdata

After that, flash again the OFox and vbmeta of RUI 2 downloaded from 1st post. Recovery is back on after reboot.

Download RUI 1 firmware, older version of OFox (R11.01) and its corresponding vbmeta files, and flashed them at recovery.

Flash back previous LOS (NOV) version with RUI 1, and everything is running fine so far.

I may try flashing again the latest version soon.

 

[xAsmodeus]

My phone is back on finally, and I may share my experience here as reference. Inspired by the post from genernal section, I have run following erase commands at fastboot to erase everything.

fastboot erase boot
fastboot erase dtbo
fastboot erase recovery
fastboot erase metadata
fastboot erase vbmeta
fastboot erase system
fastboot erase vendor
fastboot erase userdata

After that, flash again the OFox and vbmeta of RUI 2 downloaded from 1st post. Recovery is back on after reboot.

Download RUI 1 firmware, older version of OFox (R11.01) and its corresponding vbmeta files, and flashed them at recovery.

Flash back previous LOS (NOV) version with RUI 1, and everything is running fine so far.

I may try flashing again the latest version soon.

i'm stuck at fastboot bro how do you do this?