Database Info

"No SIM card - 31000" - Galaxy S5 G9000P

Recently I have flashed my S5-G9000P for the first time with the Resurrection OS RR-O-v6.0.0-20180405-klte-Official.
After working alright for the first day or so, texts would not send. Then, at the top of my screen it says "No SIM card - 31000". I don't really know much about modding phones, so here is what I tried so far:
- Resetting the phone
- Removing the SIM card then reinserting, then resetting the phone again
- Resetting my mobile data options
So far these above options haven't helped the problem. I have looked at similar threads to this and none seem to have the same problem based on their descriptions.
Thanks for your time.
Phone - G9000P Galaxy S5
Android Version - 8.1.0
Kernel version (if that's important) - 3.4.113-lineageos-g592be94 (gcc version 4.9.x 20150123 (prerelease) (GCC) ) [email protected] #1 Thu Apr 5 13:41:19 CEST 2018
{
"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"
}

Mine did that out of nowhere also. Saying no sim card was inserted or some junk. I have never flashed custom kernels so maybe that is an issue. I tried reflashing my custom rom I was running at the time (the one in my sig at the moment) and nothing. I ended up reflashing the stock firmware in odin then booting straight to recovery and reinstalling my rom and that seemed to fix it. That happened twice and thats how I got it fixed.
I have since flashed the latest stock sprint firmware and then installed LineageOS 16 and it has not happened since but I have been having a ton of other issues with the phone, on both custom sprint roms, and LineageOS so pretty sure my phone is on its way out. Might have to do a motherboard replacement. Hope not though.
Good luck and report back.

Well I can State the Facts... has happened here tooooo..... on LineageOS 16 and 15.1. The only fix that I have done, which may help, is Rebooting the Phone.
Yep, tat was the only thing I actually have done, When and IF it happens.
Same thing though, "NO SIM Card" " Corrupt Sim Card" and I Tink there was another one too. All if which, (Knowing that it was running correctly, prior this) I just rebooted. maybe once, maybe like 3-4 times. before it actually goes away.
Now, knowing the phone was running correctly is the Key , I believe. IF your in the process of Flashing, yep, maybe restart that. However, if its running right an all, no reason to do any flashing. why--- Well, was built in the First run batch of them. the phone is rather good and all, cant even see me spending over a $1,000.00 for a new phone, that's Ficking Nutz !!! I am sure, they did built it to last a life time, but what is it, a cell phone built in 2012. Before my warranty was over, I rooted, and got rid of all thre Samsung crap. Ran smooth. Been Flashing ever since.....

E.4.113-LineageOS-g592be94 mobile data not working
Hippie459MN said:
Mine did that out of nowhere also. Saying no sim card was inserted or some junk. I have never flashed custom kernels so maybe that is an issue. I tried reflashing my custom rom I was running at the time (the one in my sig at the moment) and nothing. I ended up reflashing the stock firmware in odin then booting straight to recovery and reinstalling my rom and that seemed to fix it. That happened twice and thats how I got it fixed.
I have since flashed the latest stock sprint firmware and then installed LineageOS 16 and it has not happened since but I have been having a ton of other issues with the phone, on both custom sprint roms, and LineageOS so pretty sure my phone is on its way out. Might have to do a motherboard replacement. Hope not though.
Good luck and report back.
Click to expand...
Click to collapse
You have in your signature a new rom, does that rom is working ok? The only thing that is driving me nuts is that I can’t have my data usage, I installed RR-O-v6.0.0-20180405-klte-Official on my gsm900M what do you suggest!?
Edited, i found it! just needed to edit the APN settings! i google them for my case that is Mexico, and now i have mobile data!!

Im still running lineageOS. I just havent updated my signature yet. I am going to be getting a new phone in the next week or so though. Pretty sure the motherboard (Internal storage) is taking a dump on me. Phone will work great sometimes for 2 weeks then apps start crashing like mad and only way to fix is to uninstall and reinstall and only way to fix it is to do a full wipe and reinstall the rom. Sometimes it will even start messing up within an hour or two. Things like google play services, the stock dialer, and bluetooth will randomly crash. I have tried just about everything. Different roms, going to stock software, nothing works. And when it tries to do do a backup in TWRP, it always fails in the data partition and always at different points saying it cant read the data partition or some junk. I forgot but I am giving up on it. I have another S5 but wont have it for another week or two.

S7 battery life issues on Oreo, Nougat, Stock, Superman etc.

Hello all,
Whilst there are many posts like this about battery issues, I thought I'd make my own because I've already tried all the approaches I can think of and I'd like to avoid any unnecessary confusion between posters.
I have less than 3 hours screen-on time on my Samsung S7 SM-G930F (international model) and horrific standby time, meaning I'll run out of battery before the end of the day even if I don't touch the phone at all. When I first got the phone, I got 4-6 hours screen on time and I see no reason why this should have changed so drastically. This is a somewhat recent occurrence, over the last 2-6 months (I believe it was gradual, so I can't quite pick out the time it started happening).
{
"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"
}
So far, I have tried:
Factory reset
Uninstalling all unnecessary (non-core) apps
replacing the battery
draining and recharging the battery fully
underclocking the processor
a multitude of different stock ROMs, both Nougat and Oreo
a few different Kernels
At best, playing around with these options has net me maybe a 5-15% improvement overall, much less than the 70-100% improvement I need to get back to what I had during early Nougat / late Marshmallow days.
Bar literally just getting a new phone, I would appreciate any advice you can give me.
EDIT: System2 log:

Was the flashing of different ROM's via TWRP or Odin?

Beanvee7 said:
Was the flashing of different ROM's via TWRP or Odin?
Click to expand...
Click to collapse
TWRP

I'd recommend making a full backup in TWRP, saving it to your PC, then doing a full Odin flash using all 4 firmware files. It's the only method that ensures a complete fresh start.
It will mean you have to install TWRP again, but then you can at least be sure that you've cleaned out literally everything.

Beanvee7 said:
I'd recommend making a full backup in TWRP, saving it to your PC, then doing a full Odin flash using all 4 firmware files. It's the only method that ensures a complete fresh start.
It will mean you have to install TWRP again, but then you can at least be sure that you've cleaned out literally everything.
Click to expand...
Click to collapse
I formatted internal storage via TWRP more than once though. I would have thought that would have fixed it.

I've added a System2 log for extra information in the OP

Well if you're leaving behind a modified bootable custom recovery, the device isn't clean, and could still have corrupted, fragmented, or badly partitioned boot files that affect all subsequent installs.
A full Odin flash is the closest thing to an out of the box system, it fixes almost all software bugs and issues. I can't guarantee it will fix your issue, but it's the only thing you've not done.

Beanvee7 said:
Well if you're leaving behind a modified bootable custom recovery, the device isn't clean, and could still have corrupted, fragmented, or badly partitioned boot files that affect all subsequent installs.
A full Odin flash is the closest thing to an out of the box system, it fixes almost all software bugs and issues. I can't guarantee it will fix your issue, but it's the only thing you've not done.
Click to expand...
Click to collapse
Ok. Thanks a lot. I'll try it and report back in a few days.
I'll probably need to get the latest files from Sammobile (more like Sam-slow-bile).

samfirm tool still works for obtaining the latest firmware files, and I get max speed using it on my internet (100mbs down)
For older versions you might have more luck with updato.com, for me I get almost full speed if I use a download manager, but it does have a bit of a slow start period.

hey bro i have the same issue in oreo so its not worth downgrading to 7.0 ? .... these samsung have the most lowest battery life from all phones ... god btw what is that app your using ?

dengiz-islam said:
hey bro i have the same issue in oreo so its not worth downgrading to 7.0 ? .... these samsung have the most lowest battery life from all phones ... god btw what is that app your using ?
Click to expand...
Click to collapse
Change battery in Samsung service

Finnishman said:
Change battery in Samsung service
Click to expand...
Click to collapse
Hey, I was about to open a new topic, but maybe you could answer me here I was about to change the battery I installed an app called AccuBattery when I go to health it shows that my battery health is 48% and the estimated capacity 1.429mAh is the battery dead? I don't know if those are also acurate stats what you think? when I calculated how much I lose me with apps and stuff it exactly comes out like 1.400mAh huh? ...

[ROM][11.0][OFFICIAL][OOSCAM][OnePlus 7 Pro][11.0_r20] Evolution X | Emerald

{
"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"
}
Evolution X 5.2 for the OnePlus 7 Pro [guacamole]
Code:
/*
* Your warranty is void. Or vaild, probably?
*
* I am not responsible for bricked devices, dead SD cards, Ebolation X,
* thermonuclear war, or the current economic crisis caused by you following
* these directions. YOU are choosing to make these modificiations, and if
* you point your finger at me for messing up your device, I will LMAO at you.
*/
Living, Breaking, Keep Evolving.
Pixel UI, customization and more, we are Evolution X!
- Team Evolution X -
@joeyhuab
@peaktogoo (Now RealAkito)
Reach us on Twitter! @EvolutionXROM
What are our features?
- Just flash and check "The Evolver"
single tap gesture doesn't work, WFD doesn't work and No Verizon Network Support
DO NOT FLASH GAPPS, ALREADY INCLUDED
DO NOT FLASH GAPPS, ALREADY INCLUDED
First Time Install / Clean Flash
1. Have latest OOS 10.x flashed to both slots!!
2. Download the proper flashable ZIP for your device
3. Reboot to Recovery
4. Wipe Data/Cache/System
5. Format Data (Required)
6. Flash the ROM
7. Reboot to System
8. Reboot to Recovery (Optional)
9. Flash Magisk (Optional)
10. Reboot to System and #KeepEvolving
Update / Dirty Flash
1. Reboot to Recovery
2. Download the proper flashable ZIP for your device
3. Reboot to Recovery (Optional)
4. Flash Magisk (Optional)
5. Flash the ROM
6. Reboot to System and #KeepEvolving
Light Screenshots / Dark Screenshots / Download
Donate to me! / Official Chat / Device Support
​
Android OS version: 11.0_r20
Security patch level: December 2020
Build Author: Justin Crawford
Source Code: https://github.com/Evolution-X
Kernel Source Code: https://github.com/Justasic/kernel_oneplus_sm8150
ROM Developer: joeyhuab
Thanks: npv12, spookcity138, chandu dyavanapelli, madgeniusgamer

Reserved

Screenshots by Android 10 ????

I have Evolution X android 10. And it's amazing it has so many features and modification Love it. Does EvoX 11 have all of these features and even more? keep up the good job

Wait, this has OOS cam AND is Android 11? SICK! Does normal Magisk Beta work or do we need that modded Magisk that's been floating around?

@justasic What version of the camera program?

Just a heads up, not sure if my phone is just weird, but the first wipe instructions (step 4), resulted in my device only being able to boot to bootloader and resulting in " FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" if i try to flash or do anything on CMD/fastboot now. Not sure if it's bricked or if this will happen to you, and it's obviously not a ROM issue, but just mentioning it just incase anyone is following the exact steps.

Nice ROM,so smooth,,dualboot with MSM xtended rom,
Video with OOS Cam crash,,even with shortcut,,

Parkourkid93 said:
Just a heads up, not sure if my phone is just weird, but the first wipe instructions (step 4), resulted in my device only being able to boot to bootloader and resulting in " FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" if i try to flash or do anything on CMD/fastboot now. Not sure if it's bricked or if this will happen to you, and it's obviously not a ROM issue, but just mentioning it just incase anyone is following the exact steps.
Click to expand...
Click to collapse
Dont wipe system,,just do format data

muphetz said:
Dont wipe system,,just do format data
Click to expand...
Click to collapse
Too late, I already learned the hard way bro. I'm pretty sure it was bricked since I couldn't even get into recovery, just kept booting back to the bootloader. I unbricked it and i'm & running now though. Great rom so far, I noticed the initial UI lag that seems to be common on every A11 roms I tried for the oneplus 7, but it goes away once you refresh the screen, so no big deal. A major issue for me though is that Google FI doesn't seem to activate. When I try to it just tells me "Unfortunately your Google FI service can't be activated because your account currently isn't authorized for service". Which sounds like it's an issue with my account, but when I log into fi via my desktop, nothing seems out of the ordinary, I even randomly used the sim on a t-mobile sim locked iPhone, downloaded FI and it activated without an issue. I'm gonna go back to stock & see if it happens there. Will report back in a few.
To everyone else, don't let this discourage you from trying this rom out. Like i mentioned before, great rom so far & I appreciate the upload, I loved Evolution on Pixel 3. Just need my service lol

Parkourkid93 said:
Too late, I already learned the hard way bro. I'm pretty sure it was bricked since I couldn't even get into recovery, just kept booting back to the bootloader. I unbricked it and i'm & running now though. Great rom so far, I noticed the initial UI lag that seems to be common on every A11 roms I tried for the oneplus 7, but it goes away once you refresh the screen, so no big deal. A major issue for me though is that Google FI doesn't seem to activate. When I try to it just tells me "Unfortunately your Google FI service can't be activated because your account currently isn't authorized for service". Which sounds like it's an issue with my account, but when I log into fi via my desktop, nothing seems out of the ordinary, I even randomly used the sim on a t-mobile sim locked iPhone, downloaded FI and it activated without an issue. I'm gonna go back to stock & see if it happens there. Will report back in a few.
To everyone else, don't let this discourage you from trying this rom out. Like i mentioned before, great rom so far & I appreciate the upload, I loved Evolution on Pixel 3. Just need my service lol
Click to expand...
Click to collapse
MSMTool will save your life on this, also I recommend not using Step 4. Skip to Step 5. Wiping will erase OOS off the phone.

SaintZ93 said:
MSMTool will save your life on this, also I recommend not using Step 4. Skip to Step 5. Wiping will erase OOS off the phone.
Click to expand...
Click to collapse
Unless I straight up downloaded the wrong MSMTool, the one posted here on our forums didn't seem to work for me, said something about a firmware mismatch or something and I couldn't seem to find the correct fastboot rom for my current firmware. I've never used it before though so it's highly possible I did something wrong. What worked for me was extracting the files from the latest stock OOS, dumping all the files from the payload.bin using python, then just manually flashed whichever files it pulled from the .bin.
I'm currently back on stock OOS now though & Google FI works again without any issues. I'll deff try this again on the next update.

Parkourkid93 said:
Unless I straight up downloaded the wrong MSMTool, the one posted here on our forums didn't seem to work for me, said something about a firmware mismatch or something and I couldn't seem to find the correct fastboot rom for my current firmware. I've never used it before though so it's highly possible I did something wrong. What worked for me was extracting the files from the latest stock OOS, dumping all the files from the payload.bin using python, then just manually flashed whichever files it pulled from the .bin.
I'm currently back on stock OOS now though & Google FI works again without any issues. I'll deff try this again on the next update.
Click to expand...
Click to collapse
My question would be, what type of OP7P do you have. The one from OnePlus or the one from T-Mobile? If TMO then there is a different MSMTool you will need to use.

SaintZ93 said:
My question would be, what type of OP7P do you have. The one from OnePlus or the one from T-Mobile? If TMO then there is a different MSMTool you will need to use.
Click to expand...
Click to collapse
Good question, I bought it off of Amazon like a year ago though, so I don't have a 100% answer on that. Since I've gotten the device, I was able to OEM unlock, flash twrp, magisk etc. off the rip. I even dual simmed it with Google FI & Mint together without any issues and I use the global stock .zip from the OnePlus site everytime I update. If there's a way to check for sure, deff lemme know & I'll get back at you. Message me though since this isn't really ROM related & I don't want to clutter up the thread.

Set up works fine, getting an unusal issue where the framerate is locked at 30fps, anyone else having this issue?
*Edit* Typical, I reboot to install magisk, and now it is working fine. Nevermind me!

H4X0R46 said:
Wait, this has OOS cam AND is Android 11? SICK! Does normal Magisk Beta work or do we need that modded Magisk that's been floating around?
Click to expand...
Click to collapse
You can use magisk v21.2 or the modded one, it seems the fastboot issues were fixed in v21.2.

Eagle-no1 said:
@justasic What version of the camera program?
Click to expand...
Click to collapse
OOScam version 3.8.114, I didn't focus a lot on getting camera working quite yet which is why it still has some crashes, should be getting fixed as best I can in the next few updates.

ImjustSaiyan92 said:
Set up works fine, getting an unusal issue where the framerate is locked at 30fps, anyone else having this issue?
*Edit* Typical, I reboot to install magisk, and now it is working fine. Nevermind me!
Click to expand...
Click to collapse
This framerate issue is because I am forcing 90hz from the kernel (since automatic 90hz needs some work still), just lock the device and unlock it and it will go away.

Parkourkid93 said:
Unless I straight up downloaded the wrong MSMTool, the one posted here on our forums didn't seem to work for me, said something about a firmware mismatch or something and I couldn't seem to find the correct fastboot rom for my current firmware. I've never used it before though so it's highly possible I did something wrong. What worked for me was extracting the files from the latest stock OOS, dumping all the files from the payload.bin using python, then just manually flashed whichever files it pulled from the .bin.
I'm currently back on stock OOS now though & Google FI works again without any issues. I'll deff try this again on the next update.
Click to expand...
Click to collapse
hmm I only had to use msmtool once in my experience, generally as long as you're able to get to fastboot and you've already oem unlocked, you can go back to oos usually by fastboot booting a recovery image and flashing from there. I have not heard of Google FI before so I will look into this, we just merged our January security patch so I'll be making a new release soon and it might be related to that. I've not had any issues with wiping system on my device and I keep it there in case others are looking to come from other roms. Wiping vendor would cause issues though which is why I have flashing oos there but you're welcome to skip the wiping system step as I don't believe it will cause problems since the rom flashes over system anyway.

Done all the steps. Cant connect to my home wifi, I enter password and nothing happens. Any ideas? Wifi worked before on android 11

Colors/screen messed up after flashing LineageOSMicroG (HELP)

So I unlocked, rooted, and flashed my first android and ran into this problem. I bought another G7 Power and ran into the exact same problem.
The screen/colors are all messed up.
{
"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"
}

I'm trying to retrace my steps to determine where I went wrong.
So first I try to check if the bootloader is properly unlocked. Here I run into problems.
First I tried dialing *#*#7378423#*#* but soon as I dial the last "#" the screen just goes blanc. So that didn't work
Second I tried "fastboot oem device-info" in ADB & Fastboot
So that didn't work either.
How can I determine if the bootloader is properly unlocked?

For a temporary fix,
go into the 'Display' menu in settings,
under 'Advanced' click on 'Colors' and select a different color scheme.
You can also go back to the original after that if so desired.
This fixes it for me until the next reboot.
Didn't happen with LOS 17.1, started seeing this when I went to LOS 18.1

Sigster said:
For a temporary fix,
go into the 'Display' menu in settings,
under 'Advanced' click on 'Colors' and select a different color scheme.
You can also go back to the original after that if so desired.
This fixes it for me until the next reboot.
Didn't happen with LOS 17.1, started seeing this when I went to LOS 18.1
Click to expand...
Click to collapse
This seems to have fixed it for me. I was seriously starting to doubt myself lol
Thanks allot

Same problem here. Color switch does not help.

I have the same problem.
Rocc69 said:
So I unlocked, rooted, and flashed my first android and ran into this problem. I bought another G7 Power and ran into the exact same problem.
The screen/colors are all messed up.
View attachment 5292047
Click to expand...
Click to collapse
I also found this problem. However, the remedy given as 'settings -> Display -> Advanced -> Colours -> Cycle between the Natural, Boosted and Saturated options fixed it for me until I rebooted the phone. Makes me wonder if there are some lines of coding that could be looked at with the controls of these options. Hope one of you clever guys can find a solution. Otherwise - Android 11 is working fine. Running LineageOS18.1. Thanks in advance. Ron

Looks like the problem was fixed with the LineageOS update on 10th May 2021.

Same here, no more color problems. But now I lost my modem. No cellular connection, SIM not recognized.
Edit:
Installed 2021-05-15 update OTA and cellular network came back.
Guess it could either be that the 2021-05-08 release was bad (or something went wrong during OTA)
or maybe one of my slots (a or b) has bad modem info and I will lose network with every other update.
We'll see.

As of the LineageOS18.1 May 15th 2021 update, I lost control of my SIM, the system saying that the SIM could not be found. A hard reset did not fix this either so I started afresh with boot into TWRP and wiped everything, then re-installed the first LineageOS18.1 I had downloaded to my sdcard. Voila! the system then found my SIM card again, but then when I allowed the system to upgrade to the 15th May 2021 release my SIM detection failed again! I have the wifi connection but am stumped as to what to do next. My contract is due for renewal in June 2021 so I think I'll buy a second hand Samsung instead. Any further advice anyone?

gulliverxc said:
As of the LineageOS18.1 May 15th 2021 update, I lost control of my SIM, the system saying that the SIM could not be found. A hard reset did not fix this either so I started afresh with boot into TWRP and wiped everything, then re-installed the first LineageOS18.1 I had downloaded to my sdcard. Voila! the system then found my SIM card again, but then when I allowed the system to upgrade to the 15th May 2021 release my SIM detection failed again! I have the wifi connection but am stumped as to what to do next. My contract is due for renewal in June 2021 so I think I'll buy a second hand Samsung instead. Any further advice anyone?
Click to expand...
Click to collapse
Similar to what I wrote in the comment before yours. My phone is a XT1955-5
Was on May 1st release. Lost SIM with the May 8th. Came back with the May 15th.
So it shouldn't be the May 15th release itself.
Based on what I read in a Reddit comment it could be that the modem code in one of my/our slots is bad.
I will try and confirm that by waiting for the next 2 releases to be out. Should then be such that when I install the next release I would lose SIM and with the second release get it back.
If that's the case I'll see if I can fix that without a wipe, phone is too important right now. If not I'll just live with it and only install 2 updates right after each other.

I had the same problem, somehow it works now with the new 20210515 and the old 20210508.
I suspect it has something to do with slot_a/slot_b and the respective modem bin, see my posts
here: https://forum.xda-developers.com/t/gps-not-working.4261437/
I have a XT1955-4, EU. My recollection of what I did is:
1. Flash 18.1 20210501. Modem and GPS does not work
2. Flashed modem from the original stock image like described here:https://forum.xda-developers.com/t/...nbrick-your-moto.3042687/page-6#post-80052655
3. GPS/Modem works
4. Updated to 20210508. Modem gone again.
5. Tried to flash the modem stuff again, nothing works
6. Discovered that I had forgotten to do the copypartitons part from the installation.
7. Flashed 20210501 to slot_a again, reflashed modem stuff
8. copypartions (apparently over to slot_b) / everything works like in 3
9. update to 20210508 (apparetnly to slot_b). Modem/GPS works
10. Update to 20210515, Modem/GPS works. (Microphone issue though)
Hope this helps anybody. I guess all this flasjhing could brick the phone, but it worked for me.

This issue with the messed up colours has showed up for a friend of mine as of November 2021. It is a G7 Power Dual SIM 4MB 64GB version running LineageOS 18.1
I haven't got the phone with me at this moment, but I'm happy to go to the LineageOS18.1 thread and include a logcat when I can.

Further device details to add from my comment yesterday. The Moto G7 Power is an XT1955-7
It's running the official vanilla build of LOS by @SyberHexen @erfanoabdi @npjohnson from here
The colour glitches usually appear a minute or two after reboot and after locking then unlocking the screen. Worth mentioning is I can't reproduce this screen glitch in bootloader and recovery modes.
I'm interested in the technical reason for this glitch because the image artifacts are interesting.
Attached are some photos of the phone.
sliding the RGB adjusters appear to behave normally.
Here's a picture of how a rainbow coloured wallpaper image appears when the glitch is present
Here's the original image as it should appear
The workaround solution from comment number 3 in this thread works for this device.

gulliverxc said:
Looks like the problem was fixed with the LineageOS update on 10th May 2021.
Click to expand...
Click to collapse
Nope it wasn't fixed. I have the newest update and its still there. My screen colors are " flickering" as I type this.

The problem is still there on the G7 Power that I just flashed with lineage-18.1-20220312-nightly-ocean-signed.
I also get the flickering. The fix from post 3 seems to fix it till next reboot.

Question Hard brick

{
"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"
}
If you ever get this glitchy screen there's a high chance that your device is going to get hard bricked soon. The glitches usually get accompanied by system reboots or reboots to fastboot.
We still haven't determined what exactly leads to a brick. All reports so far have been from users on stock MIUI 12.5.x or MIUI 12.5.x based custom ROMs, either with locked or unlocked bootloader. But yesterday we had the first case of a brick on AOSP too. It's probably MIUI 12.5.x firmware's fault so we suggest you to use MIUI 12.0.x if you want to use MIUI and use only 12.0.x firmware if you're an AOSP/CAF custom ROM user.
Also, make sure to take a backup of your internal storage and your apps as soon as possible if you ever encounter these graphical glitches. You'd better take backups regularly either way just to be safe.
In case you get a hard brick, you have to visit a service center to get your motherboard replaced. Do anyone faced this problem?

irmas5 said:
View attachment 5446589
If you ever get this glitchy screen there's a high chance that your device is going to get hard bricked soon. The glitches usually get accompanied by system reboots or reboots to fastboot.
We still haven't determined what exactly leads to a brick. All reports so far have been from users on stock MIUI 12.5.x or MIUI 12.5.x based custom ROMs, either with locked or unlocked bootloader. But yesterday we had the first case of a brick on AOSP too. It's probably MIUI 12.5.x firmware's fault so we suggest you to use MIUI 12.0.x if you want to use MIUI and use only 12.0.x firmware if you're an AOSP/CAF custom ROM user.
Also, make sure to take a backup of your internal storage and your apps as soon as possible if you ever encounter these graphical glitches. You'd better take backups regularly either way just to be safe.
In case you get a hard brick, you have to visit a service center to get your motherboard replaced. Do anyone faced this problem?
Click to expand...
Click to collapse
That's not a hard brick ... you screwed up your GPU/Motherboard (overheating / fake fast charger, water ... etc)
Hard Brick = bootloader relocked with a modified partition / modified firmware = Black Screen ALWAYS
you better go to a service center ... before now !!!
don't waste you time with flashing ...

I've been following this on telegram & youtube, my personal opinion is it is a hardware issue, the frequency of it happening on 12.5.x is because most people have upgraded to 12.5.x, if everyone now downgrade to 12.0.x as a 'precaution', we'll probably see reports on 12.0.x, we'll know soon enough...

No. Mine fine now. Yesterday and today started some flickering, but uninstal magisk. Fully unrooted and disappeared flickering. Just curious.

gringo80 said:
That's not a hard brick ... you screwed up your GPU/Motherboard (overheating / fake fast charger, water ... etc)
Hard Brick = bootloader relocked with a modified partition / modified firmware = Black Screen ALWAYS
you better go to a service center ... before now !!!
don't waste you time with flashing ...
Click to expand...
Click to collapse
this has been happening on all units, randomly. Do you know of any way that it can be fixed without the service centre's help?

meechyy said:
this has been happening on all units, randomly. Do you know of any way that it can be fixed without the service centre's help?
Click to expand...
Click to collapse
this is hardware issue
bricking is related to software

Lu5ck said:
this is hardware issue
bricking is related to software
Click to expand...
Click to collapse
can anything be done?

meechyy said:
can anything be done?
Click to expand...
Click to collapse
No, you send to xiaomi to service to replace the hardware.
Software fix can't cross dimension to reality.

I would expect more attention after months, if this issue were as severe, as it seems. Perhaps these were indeed hardware related issues, that weren't related to the software in any way, at all.