yashsingh1/xdaforums huggingface dataset:
[Redmi Note 11 Pro+ 5G (peux)/POCO X4 Pro 5G (veux)] MichiFirulais:
Yes, the same thing happens to me when the brightness is at 50-60% on a dark background it starts to flicker and it is not amoled black, it would be a software problem since many users have the same problem with the Poco X4 Pro 5G

I'll pass you the thread so you can read it:

https://xdaforums.com/t/poco-x4-pro...ght-spots-on-dark-black-images.4417039/page-4
[Redmi Note 11 Pro+ 5G (peux)/POCO X4 Pro 5G (veux)] FhilipeCrash:
From what I could read in this topic, the problem is that the screen does not show the true black of amoled screens, which is not my case, so much so that I tested the solution with Oreo Colorizer but it didn't work, but I've seen it in other topics some people talking about the screen flickering, including a user saying that turning off 120hz solved the problem. I hope that both issues are software related and that Xiaomi fixes this as soon as possible. Anyway thanks for the reply bro
[Redmi Note 11 Pro+ 5G (peux)/POCO X4 Pro 5G (veux)] 1qazwsx4:
This issue was introduced during the android 12 update. Previously I had no issues with flickering...
[Redmi Note 11 Pro+ 5G (peux)/POCO X4 Pro 5G (veux)] FhilipeCrash:
Well, I noticed the problem the very day my phone was updated to Android 12, so it's really a software problem. I don't know how long it will take for Xiaomi to resolve this but I hope it will be soon
[General Questions and Answers] Perceval from Hyrule:
Hello there !

I'm posting this here because I have a customer with a strange problem and I don't have the model ; I see him on monday and I try to understand what happens before.

He has a brand new Samsung I started this week, with no problem at all. There's no custom setup, but I didn't check if any update was available.

Today, he calls me to tell that about every 30 minutes, the torch led turns on and off everytime. Reboot did nothing.

I plan to clear caches, check updates and adaptative brightness, but I have no clue, I'm using Android for 10+ years, used to lots of custom firmwares up to Android 12, I never saw this.

Does anyone ever see this before ? I don't want to run a logcat from adb and lose lots of time.

Thanks and sorry for the lack of info...
[General Questions and Answers] Perceval from Hyrule:
Hi !

Well, easy target : Samsung provides a default-enabled notification on the camera torch, making the led to shine randomly, which is not a very good idea by night. This can be set in global settings, in notification tab.

Hope this helps, solved !
[Samsung Galaxy S20 FE Questions & Answers] Borna1803:
Phone got frozen while in Messenger, suddenly turned off and now it's stuck on boot loop. Holding volume down and power button does nothing, keeps it on boot loop. When I put it on charging, it heats up, but the charging logo does not show.

Anyone got any clue what might be the problem or how to solve it?
[Samsung Galaxy S20 FE Questions & Answers] 3mel:
did you receive any pictures via messenger ? that used to be a thing that messed up phones because of one colour outside most phones RGB range.

a bootloop is a cycle, catch it at the right time and you can boot into recovery to clear cache and dalvik.

remember recovery and download mode need the cable plugged into a USB device to nowadays.

the instant the screen goes off hold volume up and power and then plug the cable into the phone (the other end already being in the PC).

if you did receive a file before your problem that'll still be there and the problem might persist. you might need to boot up into safe mode and delete something.
[Samsung Galaxy S20 FE Questions & Answers] Borna1803:
The phone got frozen at the main screen of Messenger, haven't received any messages or pics.

The thing I haven't mentioned but dk if it means anything, sometimes it gets to the Samsung logo, but then it goes off and turns back on.

Tried to hold volume up and power button couple of times, sometimes it would do a strong vibration and then do nothing, but I'll keep on trying.

Thanks for ur help :)
[Samsung Galaxy S20 FE Questions & Answers] 3mel:
don't forget the USB cable, you can't manually boot recovery without it.
[Samsung Galaxy S20 FE Questions & Answers] Borna1803:
Cleared cache rn and got to home screen but it froze again and turned off.

Dk what to do anymore...
[Samsung Galaxy S20 FE Questions & Answers] 3mel:
if you don't mind losing messages next time you could try clearing data on the messages app. you'd need to be pretty quick by the sound of it.
[Samsung Galaxy S20 FE Questions & Answers] Exelier:
Well! my phone got frozen at messenger as well! Thoguh it gonna just restart and everything will be fine, but no!

Stupid chinese cheap **** Called Xiaomi!
[Introductions] Ranball:
Hello! new to the community, at least as no more as guest user. :cowboy:
[Introductions] orb3000:
Hello, welcome to XDA
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ZaroxJH:
Yesterday my Poco F3 crashed out of nowhere while I was just texting someone. Now it's stuck in a bootloop where it's constantly rebooting itself, I can only enter fastboot or recovery for like 2 seconds, after that it reboots again.

I was able to get it on later by holding all buttons, but it quickly crashed again and now holding all buttons doesn't work.

I'm running the latest version (as of now)

Edit: No the bootloader is not unlocked, it's fully unmodified.

Has anyone else had this problem?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Andreasgbrv2:
It's your phone ok now?If it's still broken,I think it's a motherboard issue or maybe a software bug.Anyways,if you are able to boot into recovery by hording power+vol up,try a data wipe:)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] TechieTwinToes:
I've had this issue in the past with Samsung phones. The root cause for those was a jammed power button. I had to give it a vigorous shake/jerk to get it back to normal but it would happen again out of nowhere. Depending on how much you actually press the button, there's a very good chance that it could be the reason.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Starboy999:
I had the exact same issue yesterday. I had wiped data from the menu and it was fixed. I don’t know why did that happen out of the blue. If any one knows what issue that is, please let me know.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Cabeção-Flu:
Happened to me today.

I pressed power button quickly for a while. Then, when rebooted in system, i disabled pin lock fast and reboot in recovery.

Wipe dalvik cache seems resolved the problem to me until now.

I'm in Xiaomi.eu 13.0.7
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] TWeaKoR:
Sounds like your hardware power button is slightly depressed. Even when you're not touching the button, it reboots every few seconds.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] extrem0:
Something different happened to me yesterday. It was clearly the power button. If I touch the power button (like for fingerprint unlock), it would identify as power button pressed. So my phone started bootlooping, but not so frequently. And power menu was showing up more frequently.

What I did to fix it was swipe a soft tissue through the side of the phone (where power and vol buttons are placed).
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] nockcx:
the exact thing happenend to me yesterday and I don´t know how to fix it. i tried to flash twrp but now my device just reboots to fastboot mode about every 5 seconds and i can´t flash anything that takes longer than that. I would be happy if someone knew how to fix this
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Cuonglla117:
If u can open the phone get the power button flex disconnect then try again to see if that fix
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Alipk52:
Hello, i have had the same issue, did you also noticed color leaking when it enters poco logo? like a color lining on the screen which changes location with every reboot? i have submitted my phone to service center, but they are telling me it's motherboard and asking cost which is more than a phone. i was texting someone too when it happened.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] L8ter:
What ?

The Poco F3 costs new actually 300 €.

They ask you for more ?

Try a local repair shop, probably a CPU issue a reballing of the CPU should not cost more than 30 to 40 €..

Everything else is a rip off..
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Alipk52:
They told me the Motherboard needs to be replaced, which is really expensive, i have said no to them and asked for a return of device, i wonder if Motherboard is faulty, how come it enters fastboot mode? I have tried recovery mode as well, it entered once, i flashed xiaomi eu update over existing and it ended with error, now i have tried to boot into recovery couple of times only but it didn't booted, i sent it to service center. I think i should have tried better with recovery or fastboot mode. Xiaomi service centers all over the world is crap and known to impose different faults even if it's not there. That's why i don't believe them.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] L8ter:
I still have my Samsung S7 Edge and from time to time, it turns itself off and you can not restart it if you press the power button.

You can boot it into Odin download mode, but nothing else.

Only if you put in the USB cable to load it, it will boot.

Also strange, I'm saying this because you asked why your device boots into fastboot mode, but nothing else

Devices are sometimes very strange and not reasonable the way the work or not.

Hope you get it fixed for reasonable costs.

Good luck buddy .👍
[Redmi 9A Questions & Answers] Reasonable_Carob_211:
Can anyone tell me about any custom ROMs which are safe to install on a Redmi 9A dandelion??
[Redmi 9A Questions & Answers] yaro666:
every custom ROM is buggy and not daily, so that phone is abandoned
[Redmi 9A Questions & Answers] the_arxyn:
Nusantara project is the only rom officialy supported for this device and its features and ui is also the best
[Xiaomi 11T Pro] krzywojc:
Hi all!,

I have now MIUI Global 13.0.10.0 and a few days ago I got an update 13.0.15.0 SKDEUXM. My question is - can I follow the procedure from MIUI 12 to do it in the same way:

What I know, it shouldn't be used during update from MIUI 12 to MIUI 13 but later?

Is here anyone who tried it?

Thanks in advance!
[Xiaomi 11T Pro] NeoDJW:
Haven't tried that way, I installed OTA , then flashed twrp again and magisk, everything done in 2mins, 10mins with update.
[Xiaomi 11T Pro] Cengiz67:
i did it this way with magisk ota , ça fonctionne nickel chrome , it's work fine
[Xiaomi 11T Pro] terry_mccann:
I flashed 15 and have no issues.
[Xiaomi 11T Pro] Hunter_Adad:
Hi, another question: Has anyone tried rooting 13.0.15? Is it the same procedure used for other 13.0.X versions?
[Xiaomi 11T Pro] krzywojc:
I have udpate just yesterday done. I have uninstalled magisk by restore image, then update WITHOUT REBOOT, then install in inactive slot and finally reboot. Just like in MIUI 12.

Further no issues!
[Xiaomi 11T Pro] samy233:
Thank's man for this tuto ! Perfect !
[General Questions and Answers] H3wastooshort:
Pretty much noob here.

I have a Galaxy S3 Neo running non-rooted LineageOS 18.1 and the TWRP bootloader. It has a broken USB circuit. The Port looks fine after taking it apart but getting power or data connected is a 1/100 chance.

Because of that I attached an external charging circuit (TP4056) and while im at it upgrade it to 3 18650 cells for fun. This setup works fine except for one issue:

Androids internal battery meter is completely useless, due to the capacity being at least 4x the original and it not being able to measure charging as that is done by an external circuit. As soon as you "empty" the battery (wich it thinks way too early), it will not go up again unless i disconnect the battery and charge it to 100%, then reconnect.

My current "fix" is to connect via network debugging and run `dumpsys battery set level 42` wich keeps the phone from shutting down and just read the voltage with a small LED voltmeter thing I glued on the back, but having to connect to my PC every reboot sucks. I tried running the same command from a terminal emulator on the android device wich just states it could not find the service 'battery' even though it works via adb and 'battery' clearly is in the services list, even from the terminal emu. I tried smuggleing the command into a /system/etc/init/*.rc file as a oneshot service via TWRP's text editor but that did not change anything, probably because i did something wrong.

Idealy the solution would

* run automatically or be otherwise permanent

* prevent shutting down

* not require recompiling lineage
[Xiaomi Poco F4 (Munch) / Redmi K40S] sendme2pop:
Post your POCO F4 Snaps here.

While posting make sure share Capture details like clicked from Stock/Gcam Version XML etc.
[Xiaomi Poco F4 (Munch) / Redmi K40S] roirraW "edor" ehT:
@sendme2pop

The standard sticky post hasn't been added to this new device section yet, but when that (Sticky post added by me just now) The sticky post in this section includes the following: Post #5 - WhatsApp/Telegram Groups and Channels - Going Forward

Please PM me if there are any questions. Thank you!

@roirraW "edor" ehT
[Xiaomi Poco F4 (Munch) / Redmi K40S] sendme2pop:
ok i am unaware of it. thanks
[Xiaomi Poco F4 (Munch) / Redmi K40S] psklf:
View attachment 5707565

Taken by Camera by Google in miui.eu rom
[Samsung Galaxy S22] dskiller:
Sorry about thread title, big fingers little keys on phone. Tried to edit and bumped damn enter key

S22 att firmware 4.1.1 question

So my phone update twice in August and the last update I thought was going to be the 4.1.1 but after updating still says 4.1 with same August 1 security.

And firmware isn't even listed on site

Which ends in 2AVHD

And buggy firmware as card game I had install was auto running everytime screen was unlocked and att games app was auto running as well
[Google Pixel 6 Pro] mkhcb:
According to google:

Fix for issue occasionally causing increased battery drain from certain launcher background activities

Downloading it now. Let's see how battery life works with this new update. I'll also add a poll.
[Google Pixel 6 Pro] Taskman:
I really hope it does. Got it yesterday so will see in a few days or a week when I gone through X charges.

Right now it can barely hold a charge during a full day without me charging a bit, to make sure it doesn't die at like 5 or 6pm

Here is to hoping I can go back to the more normal of having around 40% when I get home around 6pm and just charge it in the evening and use till the next day etc.
[ASUS ROG Phone 5 / 5s] chairman011:
Ok so y'all remember when it was possible to "boot" into twrp? Ok so of course y'all know that after a certain update you no longer can boot into twrp but you can flash it through magisk and it works fine. So my question is it possible to flash stock recovery to remove twrp?
[ASUS ROG Phone 5 / 5s] Andrologic:
Yes, your original boot.img needs to be flashed back.
[ASUS ROG Phone 5 / 5s] chairman011:
Thank you so much for the response have another question how do I go about obtaining the boot image of the latest Android 12? I want to remove TWRP that I flashed with magisk.
[ASUS ROG Phone 5 / 5s] chairman011:
Ok I was able to get it thanks again
[General Questions and Answers] NightRaven49:
hi, i have a xiaomi mi mix 2s that was running los18. one morning i woke up before my alarm, checked my phone and went back to sleep. when i woke up again, i found the phone was on the splash screen and then started bootlooping. going into orangefox recovery, i was greeted with numerous /data mount errors, namely:

Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Unable to mount storage

from what i can tell, the only way to get the device working again is to format the /data partition, which means losing all my data which im trying to avoid. i did manage to obtain a dd dump of /dev/block/bootdevice/by-name/userdata through usb otg, though ive been unable to read the img file, either through windows or ubuntu. is there any way to mount it and retrieve the data? i did specifically flash dfe from the start, so it should be unencrypted. the file system is ext4.

would also greatly appreciate other suggestions on how to recover the data.
[General Questions and Answers] NightRaven49:
bump, any input is appreciated!
[General Questions and Answers] xXx yYy:
You restore the data backed up with DD command as following

dd if=dump.img of=/dev/mmcblk0p29

assuming partition named userdata is block device named mmcblk0p29
[General Questions and Answers] alecxs:
check getprop ro.crypto.type and ro.crypto.state from adb shell. also check dump.img with xxd or hexdump has ext4 / f2fs magic 53.ef / 10.20.f5.f2 starting at 1080 / 1024 byte
[General Questions and Answers] NightRaven49:
apologies for the late reply, dont really check xda that often.

is that after wiping? wouldnt that make the data partition unreadable again?

ro.crypto.type=file

ro.crypto.state=encrypted

as for checking the dump, are you referring to the commands:

xxd -l 1080 dump.img | grep 53ef
xxd -l 1024 dump.img | grep 1020.f5f2

if so, i did not receive any output. if they are wrong commands please let me know what i should enter.
[General Questions and Answers] alecxs:
looks like (FBE) file-based encryption. if dump is really encrypted there is nothing you can do on PC.

you can only restore + decrypt on device (as long as you did not factory reset)
[General Questions and Answers] NightRaven49:
i havent factory reset as i read some things about tee keys that would be wiped during data format, so i thought it would be handy to keep if i needed them. how would i go about trying to decrypt on device though?

also, what would have been the point of flashing dfe if in the end data is still encrypted?
[General Questions and Answers] alecxs:
right, encryption is bonded to TEE (which is flushed on factory reset). just restore and let orangefox or twrp decrypt (assuming it has well implemented encryption support). otherwise your only chance to decrypt is via regular booting into android (to at least stage with lockscreen or adb).

FBE data is encrypted with screen lock credentials, remember old pin, pattern, password used at time of dump.

"dfe" stands for disable force encryption (encryption will no longer forced after formatting) and there is a good chance this is the reason for failed decrypts. you can undo by restoring vendor partition.
[General Questions and Answers] NightRaven49:
do you mean restore as in simply

dd if=/dump.img of=/dev/block/sda21

as @xXx yYy mentioned? would that make a difference? since the block device is fundamentally holding the same bits before and after doing so, at least to my understanding. im also quite apprehensive about making any modifications to the data partition as it is right now.

the phone doesnt get to lockscreen... 😢 i did enable usb debugging, but not sure if it is possible to access while bootlooping.

the thing is, i flash dfe right after flashing the rom with a data format, so i thought i would be safe from this kind of things happening. plus, i had been running this setup since the start of the year, and hadnt so much as changed any system settings recently, so its quite odd that the problem would just randomly manifest. it is not the first time it has happened either, in fact this happening the first time was what prompted me to start using dfe, so it is quite disappointing to see that it did not have its intended effect.

so to clarify, should i dd to the userdata block device and restore vendor (presumably from rom zip) or is dd enough?
[General Questions and Answers] alecxs:
yes, dd is fine (one could also use of=/dev/block/bootdevice/by-name/userdata)

and no, of course it doesn't make sense in that case.

I don't know what is the cause but I am afraid the only way to access that data is fix boot-loop.

It is unclear to me if encryption worked for a year or if you encrypted recently. Open dump with HxD and check first 1088 bytes for ext4 magic, or at least you should see many zeros on plain disk image.

Also check /vendor/etc/fstab* for flags in line /dev/block/bootdevice/by-name/userdata with notepad++ this could help to identify encryption is broken by dfe or healthy.
[General Questions and Answers] Renate:
I checked two devices offhand, one was block encrypted, the other file encrypted.

I looked at the last 1M of the partitition of the file encrypted.

I thought that there was a footer there, there wasn't.

Your original message said that it couldn't find the footer.

I know some things use footers and they are usually a specific number of blocks before the end of the partition.
[General Questions and Answers] alecxs:
@Renate unable to find crypto footer - is misleading message from orangefox twrp recovery - it always check for any type of encryption but FBE encryption requires no crypto footer (only FDE or metadata encryption)
[General Questions and Answers] NightRaven49:
so should i still do it? 😅

but it also seems that the bootloop is caused by the inability to mount data...

also it seems adb is not accessible while it bootloops.

i flashed dfe along with the rom and magisk at the start of the year, havent flashed anything since. i also did not initiate any encryption process the whole time.

it is mostly 0000 or ffff, though there is mention of ext4 map blocks a little further down.

Spoiler content hidden.

<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=0,noauto_da_alloc latemount,wait,check,=ice,quota
[General Questions and Answers] alecxs:
okay the good news it's probably not encrypted (at least no FDE) no need to decrypt disk image on phone.

the bad news it doesn't look like valid ext4 file system, you cannot mount it.

on linux pc, try fsck on dump2.img (make a copy first) then try to loop mount file. you can also try testdisk or photorec

the flag fileencryption=ice is broken by dfe (which is intended) so encryption/decryption won't work (as desired, not required on plain ext4)
[General Questions and Answers] NightRaven49:
THANK YOU SO MUCH! my data is now readable on linux, will copy as much over before doing anything else. i was legitimately not expecting it to work.

should i also dd the repaired img to my userdata block device? i know twrp/ofox has e2fsck command, seems like it may be able to repair the partition on device in a similar manner.
[General Questions and Answers] alecxs:
didn't expect it's so easy lol.. yeah try e2fsck on /dev/block/bootdevice/by-name/userdata directly first.

TWRP/Orangefox properties was bit misleading...

sometimes the solution is simpler than we think
[General Questions and Answers] NightRaven49:
same, actually the last time it happened (over 1.5 years ago) i also tried something similar, but didnt work because it was f2fs if i remember correctly. so i didnt think of trying e2fsck this time around. i suspect it may be a hardware flaw that caused it, since i am running a different rom now.

it works now, again thank you so much. funny how i was stuck without a phone for a month, went to so many data recovery specialists that told me that there was no hope and yet the fix was finished in mere seconds.
[Xiaomi Poco F4 (Munch) / Redmi K40S] roirraW "edor" ehT:
Please visit the linked thread prior to posting:

[INFO] Device Forum Rules (Please Read before Posting)

In this thread, we will provide a short Q&A for your stay on this forum. Please read thoroughly and act accordingly. While most that is needed to know is pointed out in the Forum Rules, history shows that some points of these rules are not...

xdaforums.com