Database Info

Help needed - Stock Firmware reinstallation via KIES caused Boot Loop

Hi guys.
I have a little problem with my tab now . Originally my machine had a little hiccup ever since I upgraded to Lollipop. The problem was that it tried to upgrade apps to Lollipop every time I did a boot cycle. Usually ending with a message that an app called "a...a" closed. I did not bother me much for a while. But Today I thought it was past time I resolved this so I tired to reinstall the firmware with Kies. Bad idea in retrospect, since it caused a boot loop at first (I did not touch it for 1-2 hour) than after seeing that it did not progressed. I tired a forced restart by holding down the power button. Strangely somehow after 2 or 3 tries it did started to do something. Saying that it has to update 190 apps and it did so, after then I found myself at the first setup page. However it did not worked because a lot of warnings come up constantly like: google process stopped, maps stopped, etc... making it unusable to set up anything, since even if you OK the warning the next comes up constantly. Also Kies no longer detects the phone, so I was forced to use Odin to reflash it. But here's the twist: even after reinstalling the same version of the stock image via Odin the continuous boot loop occurs again and again. (The image I got it from samdownloads de). I'm unsure where the problem can be, the only thing I can suspect is that I only used AP with Odin since the rar did not contain any bl cp csc or anything (I also tired full wipe via recovery but it did not help). So if anybody have any idea as to what direction should I take, please say so. I would really appreciate the guidance.
Disclaimer: My machine is completely stock with an untripped Knox, and it was bought from Germany.

quarros said:
Hi guys.
Disclaimer: My machine is completely stock with an untripped Knox, and it was bought from Germany.
Click to expand...
Click to collapse
Try to flash your AP file with Bootloader
http://forum.xda-developers.com/showpost.php?p=62573251&postcount=21

Beut said:
Try to flash your AP file with Bootloader
http://forum.xda-developers.com/showpost.php?p=62573251&postcount=21
Click to expand...
Click to collapse
Thanks for the tip. My problem is that I don't know how different region Bootloader relates to my machine.
The linked one is for the US version of the machine. And I'm unsure whether flashing a different region's
ROM trips the Knox or was there any difference in hardware between units sold to different region
(seems very unlikely but not impossible). My tablet is from Germany with the DBT region firmware.
So is it right to mix the two parts together?

quarros said:
Thanks for the tip. My problem is that I don't know how different region Bootloader relates to my machine.
The linked one is for the US version of the machine. And I'm unsure whether flashing a different region's
ROM trips the Knox or was there any difference in hardware between units sold to different region
(seems very unlikely but not impossible). My tablet is from Germany with the DBT region firmware.
So is it right to mix the two parts together?
Click to expand...
Click to collapse
There is no problem as all region is the same hardware, the one sold in Europe has no different than a tablet sold in US.
For example, software for UK has more languages than US, the rest is the same. I used to load UK or Korean version for the US tablet to fix Bluetooth issue, go back and forth Kitkat and Lollilop without tripping Knox as the firmware is official.
Like this one, I loaded Korean firmware to an US tablet
{
"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"
}

Beut said:
There is no problem as all region is the same hardware, the one sold in Europe has no different than a tablet sold in US.
For example, software for UK has more languages than US, the rest is the same. I used to load UK or Korean version for the US tablet to fix Bluetooth issue, go back and forth Kitkat and Lollilop without tripping Knox as the firmware is official.
Like this one, I loaded Korean firmware to an US tablet
Click to expand...
Click to collapse
Thank you so much for the info I'm sure it will come handy later on (Probably I wont be so nervous to install custom rom next time). :good:
Thankfully it is now solved even without flashing a new bootloader.
For future reference here is what I did:
I used a different freshly installed computer with Windows 7 to flash it.
I also downloaded Odin version 3.10.7 form the forum (I previously used 3.09, also downloaded from here)
I started up the Tab booting to recovery (p + home + volume up). Erased data and wiped cash.
Than immediately rebooted to Odin mode (p + home +volume down) as to not let anything written to the previously wiped partitions.
Than with Odin I reflashed it with the previously downloaded firmware I got from samdownloads de (P900XXU0BOI1_P900DBT0BOH1_HOME)
All seems working properly now. And the initial problem also went away.
Thanks again

quarros said:
Thank you so much for the info I'm sure it will come handy later on (Probably I wont be so nervous to install custom rom next time). :good:
Thankfully it is now solved even without flashing a new bootloader.
For future reference here is what I did:
I used a different freshly installed computer with Windows 7 to flash it.
I also downloaded Odin version 3.10.7 form the forum (I previously used 3.09, also downloaded from here)
I started up the Tab booting to recovery (p + home + volume up). Erased data and wiped cash.
Than immediately rebooted to Odin mode (p + home +volume down) as to not let anything written to the previously wiped partitions.
Than with Odin I reflashed it with the previously downloaded firmware I got from samdownloads de (P900XXU0BOI1_P900DBT0BOH1_HOME)
All seems working properly now. And the initial problem also went away.
Thanks again
Click to expand...
Click to collapse
From my experiences, these things have nothing to do with flashing a firmware:
1- Fresh installed windows, I use XP or Windows 7, there is nothing different as long as you have correct Samsung USB driver.
2- Odin versions have no differences, I use old or new, they are both the same.
3- Home button is not needed to access Download or Recovery Mode
Your problem went away probably from fresh install of the system.

Xiaomi Redmi 4 (prada; Standard Edition) - All info in one thread

{
"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"
}
Redmi 4 is a mid-end device released by Xiaomi (along with 4A, 4 Prime) in November 2016. The device itself is very similar to Redmi 3S in every aspect, expect it has a few improvement to some components. (For example the Wi-Fi, where 5GHz connection is now possible)
Device specs: http://www.gsmarena.com/xiaomi_redmi_4-8419.php
Available official ROMs: http://en.miui.com/download-318.html
Rooting only possible via official unlock (There is no known method for unofficial unlock)
No official Global ROM was released yet.
Redmi 4 subthread in XDA: https://forum.xda-developers.com/t/xiaomi-redmi-4
TWRP for Redmi 4: https://forum.xda-developers.com/an...fficial-twrp-recovery-xiaomi-redmi-4-t3594052
If something is bothering you feel free to express your thoughts.

Any news for the global rom for Redmi 4 prada??

VE511 said:
Any news for the global rom for Redmi 4 prada??
Click to expand...
Click to collapse
Unfortunately no
There is a Global ROM available from the official MIUI site, but it has in-calling bugs, and is not released officially.

Redmi 4 just got it's very own subforum!!
https://forum.xda-developers.com/t/xiaomi-redmi-4

Can somebody please give his QCN file from Redmi 4? I need to fix my baseband and IMEI... Thank you.

Clean android....
Hello, i'm new user on this forums. I have very big problem with my device.
I got second model of Redmi 4, first one had malfunction of SIM module (after instaling CM 13), and device wasnt detecting SIM's at all (what more interesting SD cards was detected) on both slots. After service i got brand new Redmi 4, installed CyanogenMod 13 as only properly working OS* and starting to have the same issue.
*So now let me explain why i threat CM 13 as only working OS - it uses battery as it should. On every MIUI (which seems to not be official) including MIUI 9 my battery just drain. For example with 1-2 hours of daily usage on CM my battery can keep 7-14 days, which is perfect resoult, while on MIUI even unused device is keeping max 4 days, and battery usage says Android OS and android (process names) eat 40 % of battery (sometimes up to 56%). I'm installing OS by full wipe, so its not the case of files remaining from older OS.
NOW final question to all specialists here - from where can i get CELAN ANDROID MARSHMALOW or NOUGAT for my model (Redmi 4 prada)? Installation as i understand properly is the same as in case of ROM right (TWRP) or maybe flash?
Please answear, i'm looking over internet 2 months right now, and spending all my free time after job on unsuccessfull searching for help.

Hello,
After I flashed my phone to MIUI 9 (can't remember which one - so many I tried), I got the success message on MiFlashTool, but my phone didn't restart. It was dead.
I mananged to revive it but I had lost many sensors, like wi-fi, bluetooth, etc. I managed to fix those and then I was getting an error about IMEI (can't ID the device) or something like that. Basically my IMEI was gone. I found a fix for that. The phone can now detect the SIM card.
My issue is that it can't connect to the GSM network of my carrier.
I double checked the APN settings - they are good. When I dial *#*#4636#*#* I see the 'turn radio on' button but it doesn't do anything.
Switching back and forth between different versions of MIUI did not help. I tried flashing the NON HLOS bin file via command prompt, I got the okay message, but it didn't fix the problem. I tried flashing the 3 modem files via TWRP, again, it didn't fix my problem.
They talk about restoring EFS on a thread, but I don't know how to do that or if that will help. I don't have the back up files anyways for EFS.
Can anyone help?
Currently I am on CyanogenMod 13 (OS 6.0.1).
Thanks
Andrei

camilleisfunky said:
Hello,
After I flashed my phone to MIUI 9 (can't remember which one - so many I tried), I got the success message on MiFlashTool, but my phone didn't restart. It was dead.
I mananged to revive it but I had lost many sensors, like wi-fi, bluetooth, etc. I managed to fix those and then I was getting an error about IMEI (can't ID the device) or something like that. Basically my IMEI was gone. I found a fix for that. The phone can now detect the SIM card.
My issue is that it can't connect to the GSM network of my carrier.
I double checked the APN settings - they are good. When I dial *#*#4636#*#* I see the 'turn radio on' button but it doesn't do anything.
Switching back and forth between different versions of MIUI did not help. I tried flashing the NON HLOS bin file via command prompt, I got the okay message, but it didn't fix the problem. I tried flashing the 3 modem files via TWRP, again, it didn't fix my problem.
They talk about restoring EFS on a thread, but I don't know how to do that or if that will help. I don't have the back up files anyways for EFS.
Can anyone help?
Currently I am on CyanogenMod 13 (OS 6.0.1).
Thanks
Andrei
Click to expand...
Click to collapse
I'll transfer cash via paypal to whomever walks me through the process. Thanks

camilleisfunky said:
Hello,
After I flashed my phone to MIUI 9 (can't remember which one - so many I tried), I got the success message on MiFlashTool, but my phone didn't restart. It was dead.
I mananged to revive it but I had lost many sensors, like wi-fi, bluetooth, etc. I managed to fix those and then I was getting an error about IMEI (can't ID the device) or something like that. Basically my IMEI was gone. I found a fix for that. The phone can now detect the SIM card.
My issue is that it can't connect to the GSM network of my carrier.
I double checked the APN settings - they are good. When I dial *#*#4636#*#* I see the 'turn radio on' button but it doesn't do anything.
Switching back and forth between different versions of MIUI did not help. I tried flashing the NON HLOS bin file via command prompt, I got the okay message, but it didn't fix the problem. I tried flashing the 3 modem files via TWRP, again, it didn't fix my problem.
They talk about restoring EFS on a thread, but I don't know how to do that or if that will help. I don't have the back up files anyways for EFS.
Can anyone help?
Currently I am on CyanogenMod 13 (OS 6.0.1).
Thanks
Andrei
Click to expand...
Click to collapse
Wow, you really mess up bro...
Let's see... First I advise you to flash the official fastboot ROM from the official forum and see if boot normaly.
If not, you can try unbrick the phone by 'test points'.

Hey
Thanks. The phone boots normally, everything works except for the radio. All commands for the radio can't be changed. If I do *#*#4636 phone information, I see my SIM Card, it shows my carrier (Rogers). WHen I click the 3 little buttons to select the band it shows unknown and lists a few options, including the one I think it the one I need (GSM 850/1900 - i'm in Canada). When I select that band it shows unsuccessful....What can it be?

camilleisfunky said:
Hey
Thanks. The phone boots normally, everything works except for the radio. All commands for the radio can't be changed. If I do *#*#4636 phone information, I see my SIM Card, it shows my carrier (Rogers). WHen I click the 3 little buttons to select the band it shows unknown and lists a few options, including the one I think it the one I need (GSM 850/1900 - i'm in Canada). When I select that band it shows unsuccessful....What can it be?
Click to expand...
Click to collapse
I must admit that is out of my league.. Sorry
You saying the radio is turned off and can't receive calls? You don't have signal?
In the 'Phone Information', in the button of the page, there is a option that say 'Turn Radio On/OFF', try it.
But... You say you have some modem files, right? If is the same I used when I change to a custom ROM, maybe can help. Try flashing that files in TWRP.
---------- Post added at 01:18 AM ---------- Previous post was at 12:58 AM ----------
DracoXXI said:
I must admit that is out of my league.. Sorry
You saying the radio is turned off and can't receive calls? You don't have signal?
In the 'Phone Information', in the button of the page, there is a option that say 'Turn Radio On/OFF', try it.
But... You say you have some modem files, right? If is the same I used when I change to a custom ROM, maybe can help. Try flashing that files in TWRP.
Click to expand...
Click to collapse
Sorry, I remember now one thing...
Which fastboot ROM you use? China Stable or Dev?
Try use the Dev ROM and in Miflashtool, select 'Clean All' option.
Hope this work

DracoXXI said:
I must admit that is out of my league.. Sorry
You saying the radio is turned off and can't receive calls? You don't have signal?
In the 'Phone Information', in the button of the page, there is a option that say 'Turn Radio On/OFF', try it.
But... You say you have some modem files, right? If is the same I used when I change to a custom ROM, maybe can help. Try flashing that files in TWRP.
---------- Post added at 01:18 AM ---------- Previous post was at 12:58 AM ----------
Sorry, I remember now one thing...
Which fastboot ROM you use? China Stable or Dev?
Try use the Dev ROM and in Miflashtool, select 'Clean All' option.
Hope this work
Click to expand...
Click to collapse
Thanks. I tried all those things many times before. My radio functionality is faulty. I cannot enable the radio.

camilleisfunky said:
Thanks. I tried all those things many times before. My radio functionality is faulty. I cannot enable the radio.
Click to expand...
Click to collapse
Then only by test points, don't see any other options.. At least for now..

What is the benefit of using test points vs fastboot?
Thanks

camilleisfunky said:
What is the benefit of using test points vs fastboot?
Thanks
Click to expand...
Click to collapse
Well... The test points is more for when the phone is really mess up, phone don't boot, not enter the 'fastboot', etc... normally know as 'hard brick'. It's the "ultimate" recovery.
In the PM I send to you, there is a link to a post in the official forum explaining where, and 'how to' do.
But... If you are not comfortable doing that, then, don't do.
Anyway... I can't help you more, sorry
Try asking in the official forum for help. They are more active than here.

Hope For MIUI 8 (MM) Volte support

I seen Hope for Volte working MIUI8 MM Need Dev. Support
{
"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"
}

xperiaworld said:
I seen Hope for Volte working MIUI8 MM Need Dev. Support
View attachment 4151759
View attachment 4151760View attachment 4151761
Click to expand...
Click to collapse
r u working on this rom ??

how you got the sim cards And Networks showing up in status bar because it was a bug sim cards and network not showing up in status bar but it does show up in settings ??

The project has been probably abandoned so AFAIK no more updates. Even the thread of the ROM is closed.

krishna8691 said:
how you got the sim cards And Networks showing up in status bar because it was a bug sim cards and network not showing up in status bar but it does show up in settings ??
Click to expand...
Click to collapse
Read MIUI rom thread carefully u got the answer...

tywinlannister7 said:
The project has been probably abandoned so AFAIK no more updates. Even the thread of the ROM is closed.
Click to expand...
Click to collapse
Ya but I never give up...It's need soMe R& D .....I m not developer of the rom but I still love to play around it..Hope somebody ready to work on it with me...

can anybody upload it to mirror......i cant find the download anywhere....

rajvansh said:
can anybody upload it to mirror......i cant find the download anywhere....
Click to expand...
Click to collapse
Wait i will post .... Link i found on net....
But i suggest wait for fix..

xperiaworld said:
Wait i will post .... Link i found on net....
But i suggest wait for fix..
Click to expand...
Click to collapse
if u can give link me and my friend can also try to fix bugs.....currently we r working on miui for samsung s5 exynos

xperiaworld said:
Read MIUI rom thread carefully u got the answer...
Click to expand...
Click to collapse
i followed the steps mentioned in the thread but it didnt showed up and i have tried this many times when i installed the rom first time

After restart device quickly double press power button then unlock your phone if locked..It's work for me

Not sure how effective is this method. But worth giving a try partially worked for me.
Based on few posts I came across claiming for working VoLTE.
Note:- Quite a lenthy and time consuming method
Prerequisite :- 1) Stock MARSHMALLOW
2) Stock NOUGAT
3) MIUI
4) TWRP​According to these posts if you flash MIUI over the Stock nougat(not the soak test) VOLTE should work fine.
Doing so will loose the fingureprint functionality (since it requires stock MARSHMALLOW).
Again doubting on the Volte but I got my fingerprint sensor working(flashed over nougat soak test).
Give a try to this.
[*]1) Backup your Data.
[*]2) Downgrade to Stock MARSHMALLOW.
[*]3) Install TWRP
[*]4) Flash MIUI.
[*]5) Complete Intial setup and configure fingureprint sensor (you will be unable to modify afterwards hence configure as many figures as you want).
[*]6) Go to TWRP backup (MIUI) this rom(Store it on external drive or sd card).
[*]7) Again Downgrade to MARSHMALLOW.
[*]8) Upgrade to Stock Nougat (not the soak test one)
[*]9) Install TWRP
[*]10) Restore (MIUI)​
Hopefully this should work. (I didnt tried on Stock Nougat but on Nougat soak test Fingureprint sensor is working properly)

can u share download links......as its been asked several times by sevral user...still no one replies

bravolol said:
can u share download links......as its been asked several times by sevral user...still no one replies
Click to expand...
Click to collapse
rajvansh said:
can anybody upload it to mirror......i cant find the download anywhere....
Click to expand...
Click to collapse
Sorry for late..I have to search lot for it..Bcoz my pc is dead
MIUI8 moto g4 plus https://drive.google.com/file/d/0B78Lx-mWxGVCWDgyZFQwdTJBQmM/view

xperiaworld said:
Sorry for late..I have to search lot for it..Bcoz my pc is dead
MIUI8 moto g4 plus https://drive.google.com/file/d/0B78Lx-mWxGVCWDgyZFQwdTJBQmM/view
Click to expand...
Click to collapse
thanks bro......
:good::good::good::good::good:

SMARTHACKER67 said:
Not sure how effective is this method. But worth giving a try partially worked for me.
Based on few posts I came across claiming for working VoLTE.
Note:- Quite a lenthy and time consuming method
Prerequisite :- 1) Stock MARSHMALLOW
2) Stock NOUGAT
3) MIUI
4) TWRP​According to these posts if you flash MIUI over the Stock nougat(not the soak test) VOLTE should work fine.
Doing so will loose the fingureprint functionality (since it requires stock MARSHMALLOW).
Again doubting on the Volte but I got my fingerprint sensor working(flashed over nougat soak test).
Give a try to this.
[*]1) Backup your Data.
[*]2) Downgrade to Stock MARSHMALLOW.
[*]3) Install TWRP
[*]4) Flash MIUI.
[*]5) Complete Intial setup and configure fingureprint sensor (you will be unable to modify afterwards hence configure as many figures as you want).
[*]6) Go to TWRP backup (MIUI) this rom(Store it on external drive or sd card).
[*]7) Again Downgrade to MARSHMALLOW.
[*]8) Upgrade to Stock Nougat (not the soak test one)
[*]9) Install TWRP
[*]10) Restore (MIUI)​
Hopefully this should work. (I didnt tried on Stock Nougat but on Nougat soak test Fingureprint sensor is working properly)
Click to expand...
Click to collapse
Still volte not works..

xperiaworld said:
Still volte not works..
Click to expand...
Click to collapse
Whats steps you followed.
+
can you validate what this fellow has to say, Due to limited internet i am unable to do so,
https://forum.xda-developers.com/moto-g4-plus/themes/how-to-fix-volte-data-service-hotspot-t3598177

So I need some help and I'm hoping someone here can help.
I've tried, probably 5 or 6 times to flash this rom, but to no avail.
Every time I flash it it says "no sim card"and I know there is an issue with the SIM card error, it's been mentioned many times here. However when I do go into the settings, and I go into "about phone, under "SIM card settings" it shows "no SIM card". During initial set up, I get a pop-up that says 'IMEI cannot be verified." It also says "unknown" for network status (in sim settings). I have no data connection, nor does the phone connect whatsoever (I tried calling a few numbers; no luck).
I've tried flashing just the MIUI rom after a full wipe (including system, dalvik, cache and data) - no luck.
I've tried flashing from both MM and N rom's, doing only a cache and data wipe - no luck there either.
I'd really like to be able to get this rom going on my phone.
Any help or advice is much appreciated. Please, and thank you.
Sent from my Moto G4 Plus using XDA Labs

ricky.smitts said:
So I need some help and I'm hoping someone here can help.
I've tried, probably 5 or 6 times to flash this rom, but to no avail.
Every time I flash it it says "no sim card"and I know there is an issue with the SIM card error, it's been mentioned many times here. However when I do go into the settings, and I go into "about phone, under "SIM card settings" it shows "no SIM card". During initial set up, I get a pop-up that says 'IMEI cannot be verified." It also says "unknown" for network status (in sim settings). I have no data connection, nor does the phone connect whatsoever (I tried calling a few numbers; no luck).
I've tried flashing just the MIUI rom after a full wipe (including system, dalvik, cache and data) - no luck.
I've tried flashing from both MM and N rom's, doing only a cache and data wipe - no luck there either.
I'd really like to be able to get this rom going on my phone.
Any help or advice is much appreciated. Please, and thank you.
Sent from my Moto G4 Plus using XDA Labs
Click to expand...
Click to collapse
You just have to reboot one time when you have this issue and then, you can achieve setup wizzard.

murigny64 said:
You just have to reboot one time when you have this issue and then, you can achieve setup wizzard.
Click to expand...
Click to collapse
I just tried that, still no luck. No phone or data connection. I even tried the "double tap" power button truck; didn't do anything. ?
Sent from my Moto G4 Plus using XDA Labs

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 Massive system storage use on Stock OnePlus 9 5G

Hey everyone. I've been looking through Forum posts everywhere and can't seem to see anything recent concerning this issue that actually solves it.
My system data is taking up an extremely abnormal amount of space. So much so that I have to routinely prune my already limited photo, video, and file storage or my device runs out of space to store temp and application files. Has anyone found a decent way to fix this outside of starting from scratch?
I have a stock OnePlus 9 5G running Android 12 (LE2115_11C.48), tho it had been an ongoing issue since before Android 12...
{
"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"
}

It seems like a known issue that has no resolution but factory reset and switch to a non-OOS ROM.
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
There is some suggestion that it's dump files being constantly created.

Hmmm... Do you know if root is possible without factory reset? I bet I could find the problem files pretty quick if I could get access to those files.

dallen.baldwin said:
Hmmm... Do you know if root is possible without factory reset? I bet I could find the problem files pretty quick if I could get access to those files.
Click to expand...
Click to collapse
Not that I'm aware of. Temp root exploits are closed pretty quickly once discovered and the act of unlocking the bootloader causing the phone to be wiped is a security mechanism since having an unlocked bootloader could potentially give way to an easier method of extracting your data off of the device.

until support arrives, there's no choice but to reset and reinstall OS.
the problem with the other option of using a custom OS is kinda scary.
because installing/using a custom OS is no longer as straight forward as previous like in oneplus 3t.

jmadiaga said:
until support arrives, there's no choice but to reset and reinstall OS.
the problem with the other option of using a custom OS is kinda scary.
because installing/using a custom OS is no longer as straight forward as previous like in oneplus 3t.
Click to expand...
Click to collapse
What's scary about it? It's really not that bad as long as you read the instructions. I have flashed this thing 3 or 4 times now and it's no worse than any other phone I have ever had.

That's good to know. I previously had a Xiaomi Mi Mix 3 (may it rest in peace) and ran several custom ROMs on it before its untimely demise. I imagine the process on this device is equally nerve wracking the first couple of times and totally normal afterwards.
Any suggestions while we're on the topic?

dallen.baldwin said:
That's good to know. I previously had a Xiaomi Mi Mix 3 (may it rest in peace) and ran several custom ROMs on it before its untimely demise. I imagine the process on this device is equally nerve wracking the first couple of times and totally normal afterwards.
Any suggestions while we're on the topic?
Click to expand...
Click to collapse
If you can type fastboot commands into command prompt, it's really not that difficult. I actually often found flashing with TWRP to be more irritating because of weird errors and sometimes it would refuse to factory reset and make a really big mess for me.
Now you just download the ROM and the recommended recovery, flash the recovery, boot to recovery, flash ROM, and you're done. Obviously read each ROM's instructions though because some like StagOS require you to do other stuff (you have to flash a partition file with that one).
I personally recommend StagOS. The only thing I found wrong with it was that it didn't support Verizon (no signal with a Verizon network SIM) but the dev is working on that and the fingerprint sensor icon wasn't lined up properly which apparently not everyone had that problem. I have tried a few others and had different issues with each of them. Derpfest is pretty good too but sometimes my apps act like I have never run them and I had a weird crash when swiping down on the status bar earlier. I plan to go back to StagOS. In fact, I am going to just go ahead and do that right now.
If you want to save yourself some annoyance, if the phone doesn't have OOS 12 on it when you get it, don't flash it to OOS 12 or you'll have to downgrade it to make sure you have a firmware match.

Dang.. I thi k I already went to OOS 12 since I'm on Android 12

dallen.baldwin said:
Dang.. I thi k I already went to OOS 12 since I'm on Android 12
Click to expand...
Click to collapse
Yep, you definitely did. The easiest way to get back to being ready IMO is to run the global MSM tool to get back to OOS 11, then when that's done, unlock the bootloader (make sure you do it in this order, I had my phone refuse to boot twice when I unlocked the bootloader after installing 11.2.10.10), then when the phone has booted back up, install 11.2.10.10 OTA for global (it's in the pinned update post), then you're ready for custom ROMs.

EtherealRemnant said:
Yep, you definitely did. The easiest way to get back to being ready IMO is to run the global MSM tool to get back to OOS 11, then when that's done, unlock the bootloader (make sure you do it in this order, I had my phone refuse to boot twice when I unlocked the bootloader after installing 11.2.10.10), then when the phone has booted back up, install 11.2.10.10 OTA for global (it's in the pinned update post), then you're ready for custom ROMs.
Click to expand...
Click to collapse
When you go back to os 11 you will experience duplicate media storage issue.. I just flashed os13 stable currently shows 7GB of data on ' others ' , don't know if will continue grow..keep my eye peeled..