yashsingh1/xdaforums huggingface dataset:
[Realme 7 Questions & Answers] said1219:
I immediately switched to Samsung after that incident, although I keep my bricked Realme charged regularly, hoping that RUI 3.0 flashed on top of the flicker-bricked phones will fix the phone.

I considered getting a cheaper Samsung (priced like Realme), but after considering the performance penalty and remembering that I upgrade my phone biannually, I got the S20 FE which are priced twice as expensive but I plan to keep using this for 4 years.

Half a year ago I came to largest Realme Service Center in Jakarta, considered their Level 3 support desk nationally, and had a screaming match over this issue.

ADB should be run in the lockscreen, the screen that "flickers" upon boot finish. Not in the recovery mode as per your photo.

Have you reinstalled Windows on your PC? Since reinstalling Windows erases the ADB keys if not backed up properly from user folder.

How long since you last connected your phone to your PC? If I remember correctly, unused ADB keys are automatically deleted after a period of time from your phone.

And I think you need to either pick MTP or PTP to allow ADB. "Allow charging only" disables data exchange entirely. This is to prevent an attack like this: a public USB charging port is provided at a public location, e.g. airport. Unbeknownst to the user, the charging port is connected to a laptop which then automatically tries to pull the entire content of any device connected to it. "Allow charging only" will cause the laptop to see nothing, exactly like your photo that said "no device attached", although in your case I suspect it's due to the device not being in normal booted state.
[Realme 7 Questions & Answers] Quasar.Illumia:
Just few days ago like literally a day before the incident, and yeah I think the adb keys resets but idk about that since its just 3 days as of now

And this one is my only problem, the mtp thing should asks the user of the phone to allow a device do a "file transfer" right? I can't do that due to the screen doing the flicker thingy. Idk about your de ice but my lappy can't read my phone without it

Edit: also question, does the adb key resets depending on laptop used?

And also my phone again is realme 6 pro, does reformating my phone guaranteed to fix this?I think Im out of options since I saw posts about the OTA thingy not fixing this too and my online classes are near too :(
[Realme 7 Questions & Answers] said1219:
The phone will default to the last option selected. If you already selected PTP/MTP previously it should reappear.

Of course it does. The ADB key is generated unique for each user. Even the same laptop, if being used by different user, or the laptop is reinstalled, the phone will reject the RSA key for ADB. Using another laptop is totally out of question.

If you're ready to lose your data then yes, it should fix it.
[General Questions and Answers] Lomxitrum:
Hep how to root android 11 samsung a30
[General Questions and Answers] :
To get Android OS rooted ( have superuser access to be able to control various aspects of Android OS ) means you need to perform a certain modification that will root your phone's Android OS.

Here is what you have to do to root your device's Android OS: Replace Android OS's Toybox binary - what is a restricted version by default - by unrestricted Toybox v0.8.5. This can get achieved by means of ADB.
[General Questions and Answers] Lomxitrum:
please guide. image. video please
[General Questions and Answers] Lomxitrum:
Có thể root theo cách thông thường không? odin = twrp = magisk ... nếu bạn có thể cho tôi tệp twrp dành cho a30 android 11 và magisk của nó
[General Questions and Answers] :
Never made use of TWRP nor Magisk. :)
[General Questions and Answers] Lomxitrum:
If you root with magisk, you can't upload mod rom because there is no twrp
[General Questions and Answers] :
Why are you telling me this?
[Samsung Galaxy S21 Ultra] numotsu28:
Hi, i am really frustrated right now. i have an s21 ultra(sm-g9980) hong kong version. Been using this phone for months now with everything working smoothly. i recently received the recent security update for the phone and i updated it. thats where my problem started. after the update all of a sudden i cant receive any service at all from my sim cards. The phone displays a sort of "no entry" symbol at the top. i have tried everything. From resetting the networks to hard resetting, all to no avail. Even sent it to a local repair shop and they couldnt tell what the problem is. The imei is visible and the phone can recognise that there is a sim card in it, however, it still displays no service. this has made me really frustrated as i cant seem to figure out what the problem is. Also, i should add that however i did have a problem with my usb port which was fixed and replaced before this issue started after the firmware update. Do you think this issue is connected to the usb i had replaced? Saw a post which said something about the antenna and the usb connector being on the same daughterboard. Could this be the problem? Would really apprecaite it if anyone could help me out. thanks
[Samsung Galaxy S21 Ultra] ione2380:
Try another sim card.
[Samsung Galaxy S21 Ultra] numotsu28:
Doesnt work. Flashed another firmware. Still didnt work
[Samsung Galaxy S21 Ultra] ione2380:
I'm sorry, but it's most likely a hardware problem.
[Samsung Galaxy S21 Ultra] amirage:
Rush to the nearest Samsung repair centre and get your motherboard replaced.
[Samsung Galaxy S21 Ultra] numotsu28:
alright. Thanks
[Nexus 5 Q&A, Help & Troubleshooting] IAJWasTooShort:
When I try and flash crDroidAndroid-7.1.2-20171120-hammerhead-v3.8.3 and boot it up I get "CrDroid Home Keeps Stopping". If I try it with GApps it gets stuck in a setup loop, and if I try a newer version I get error 255 in TWRP when trying to flash it.

Does anyone know how to fix these issues?

Thanks
[P3600 ROM Development] mosec:
Can anyone please help!

I can't get my sim contacts not to show but I can't seem to be able to doit. I tried schaps config and registry editors but as soon as I reboot the device the sim contacts are back (and registry values obviously).

Any ideas?

[ROM]*[WWE] new ervius 5.2.22222 build 22222 aku 2.2.2 blu angel
[P3600 ROM Development] ervius:
it's becouse the registry key is stored into 2 provxmls files, that at startup are loaded, try, overwritting into ppc' s "\windows" folder esixting by the ones that I attack on this post

bye!!! ;)
[P3600 ROM Development] mosec:
Ervius, I tried i it but with no results. Could it possibly be because of your message about licensing the rom? I haven't installed your licence cab yet.

If anyone else has a suggestion please help. I haven't had this issue beforee with other roms
[P3600 ROM Development] chanvi93:
NikiSimFix

Hi

Try this little soft , install it in Main Memory , it work for me .
[Android Head-Units] WorriedMushroom:
I have just installed a new headunit into my Kia. Everything works fine except wifi which I cannot manage to turn on. When I try turning it on it immediately turns off. Bluetooth works normally. I have tried restarting the unit, clearing cache, deleting wifi information.. everything to no avail. Does anyone know what I can do?

Thanks.

This is the exact headunit: https://www.amazon.de/dp/B08BK3XYFJ...t_i_ACPKTSHG3PB4ZVK86NEV?_encoding=UTF8&psc=1

About machine

Build number: 202106011022

Kernel version: 4.19.111

#231 Fri 05 28 11:32:21 CST 2021

uboot-05 11 2021-17:51:59_M11 1280X720

MCU version:

CSN2_04282021_173906_V102

CPU and Memory size:

64-Bit 8-Core Cortex-A53 1.5 GHz

4GB

Model and hardware:

Model: PX5

Android version:10

SIM STATUS: not availible

IP address: unavailible

Wi-Fi MAC address: unavailible
[Android Head-Units] ExtremeMOD:
Unfortunately, this is a common problem. If you recently bought the unit - return it. The issue is with faulty hardware.
[Android Head-Units] Bob_Sanders:
Do you have the head unit's hotspot turned on? You can't run HOTSPOT and WIFI at the same time.
[Samsung Galaxy S21 Ultra] afonsov:
Hello,

Last night I installed an OTA update (G998BXXU3AUGM) for CSC TPH.

I have a Samsung Clear View cover, and for some reason it stopped working. S21 doesn't recognize it.

After googling, I found that a cache wipe could solve this issue, however, I can't access the recovery menu (volume up + power buttons and the USB cable connected to the PC).

Did this happened to anyone? Any solution for this?

Thnks,

Afonsov
[Samsung Galaxy S21 Ultra] GeckoFire:
Not specifically with Clear View cover, I did get issues with USB-A connections to a PC following OTA AUGM update on BTU, if relevant try with a USB-C to USB-C cable.
[Samsung Galaxy S21 Ultra] afonsov:
Ok, I'll try that, thanks.
[Samsung Galaxy S21 Ultra] ione2380:
Try to access recovery menu by adb command. "adb reboot recovery", without the quotes.
[Samsung Galaxy S21 Ultra] afonsov:
Thanks. Wiped cache but it didn't solve the ClearView problem. Still not working.

Next step, probably I will backup and reset the phone.
[Samsung Galaxy S21 Ultra] ione2380:
Before you reset, turn of case related settings, take the case off, reboot the phone, put the case back on and re-enable from settings. That is if you didn't already tried it.
[Samsung Galaxy S21 Ultra] afonsov:
I did all that. The weird thing is that in the settings (advanced) there is nothing related to Clear View, and I don't remeber if there was some spectific settings before this last OTA update. I have the Always On Display on. This never happened before after an update.
[Samsung Galaxy S21 Ultra] TheNewGuy92:
simplest thing is to submit error report to Samsung Members for help :/
[Samsung Galaxy S21 Ultra] blackhawk:
Samsung will eventually correct it.

I wouldn't go too nuts yet...

A factory reset likely will do nothing but waste time. If a factory reset works it was likely a settings issue although it may be a hidden setting that's not normally accessible.
[Samsung Galaxy S21 Ultra] mzsquared:
It should be under Accessibility:

Go to Settings > Accessibility features > Smart Cover, and enable Smart Cover. If the flip cover comes with a display window, enable Use display window as well.
[Samsung Galaxy S21 Ultra] afonsov:
There's no such entry pn Accessibility. In the meantime I reseted and used Odin to reinstal latest firmware but still not working. After googling, I found that this happened before to a lot of people after other updates. They didn't find a way to solve it. I'm sure it is a software problem because the cover was working before this August update.
[Samsung Galaxy S21 Ultra] afonsov:
Yes, I think I'll do that. Already reseted my S21 and used Odin to install the previous version and also the last one. Nothing solved the problem.
[Samsung Galaxy S21 Ultra] mzsquared:
I sold my S21U just last week so I can't look into that physically but I was using S-view since N10+ and that's what I remember about the settings, something went amiss w/ the latest update I guess. Could it be related to AOD? These things are somewhat related I think.
[Samsung Galaxy S21 Ultra] afonsov:
After reinstalling the latest version of One UI using Odin, tried AOD on and off. Also with NFC. No difference. My wife has a S20 FE with a Clear View Cover, so I can compare settings, but apparentely there are is no specific configuration for the cover. Maybe it is something related to some magnetic or proximity sensor used by the cover. I really don't know. But I googled and found other people with the same problem asking for help from Samsung support but it seems no one found a fix or a solution from Samsung.
[Samsung Galaxy S21 Ultra] afonsov:
This problem is solved. The ClearView cover must have some magnets or passive sensors that stoped working. I bought a new case, same model, and the new one works perfectly. It wasn't anything related to One UI. Although it is a nice cover, I don't recomend it because it may stop work with no way of checking if it is detected or not. In my case, as a coincidence, it happened at the same time I did the last OTA August update.
[Xiaomi Mi 11 Lite 4G] asakurato:
So, 12.5.4 update just came out for Global version yesterday. While it is seemingly only security update, I noticed that display color scheme for Auto was renamed to Vivid, so I thought something must have changed on black crush situation. I tested multiple videos with dark backgrounds (from low res to high res). None of them had any black pixels. Tested on both light and dark mode. So I think it's finally fixed? Anyone else tried?
[Xiaomi Mi 11 Lite 4G] denzelle24:
Not fixed
[Xiaomi Mi 11 Lite 4G] asakurato:
I barely see anything. Definitely no black pixels as before.
[Xiaomi Mi 11 Lite 4G] Nisar Ahmed Nisar:
Yes, I can also confirm it is fixed, no black crush in menu or videos. It is clear everywhere. I wonder why did not they acknowledge it in changelog.
[Xiaomi Mi 11 Lite 4G] njaya95:
Because they know they messed up and didn't wanna acknowledge both the problem and the fix 😉
[Xiaomi Mi 11 Lite 4G] Nickilauda:
It's September, 18, MIUI 12.5.4 global and its definitely not solved. It's a shame for xiaomi, my last phone from that ****ty company.
[Xiaomi Mi 11 Lite 4G] asakurato:
Ok, I have been checking on a same video on each update. It definitely has been improving and now after today, on 12.5.6, I think it's fixed for real real.
[Xiaomi Mi 11 Lite 4G] kuber24:
How this solution works? Is true black no more true as in "screen Ballance" app solution? Or not ideal black colors are darker? I don't know if i explained understandable...
[Xiaomi Mi 11 Lite 4G] asakurato:
I don't know how it works, but I don't see black pixels instead of dark background anymore.
[Xiaomi Mi 11 Lite 4G] ckret:
Not fixed in 12.5.5.0 RKQEUXM
[Xiaomi Mi 11 Lite 4G] X-man1456:
In 12.5.6 Global fixed it
[Xiaomi Mi 11 Lite 4G] Denzki87:
No it didn't fix the black crush. It is just screen balance, your oled display will be useless. Black crush will never be fix in update software it is a hardware issue in the case of mi 11 lite. F#ck Xiaomi
[Xiaomi Mi 11 Lite 4G] Tony D.U.Y:
I updated to 12.5.6 and it ONLY got fixed when:

_ Refresh Rate down to 60Hz

_ Auto Brightness off
[Xiaomi Mi 11 Lite 4G] Puremin0rez:
I have purchased two Mi 11 Lite 4Gs, one is running 12.5.1 and the other 12.5.6. I'm in an interesting situation where I can directly compare both screens next to each other.

The one running 12.5.6 has much deeper blacks, and does not have the weird green tint. The text also looks more crisp which is interesting... definitely confirmed that. The manufacturer date is April, 2021.

The one running 12.5.2 has no deep blacks, and has a weird green / hazy gray tint. It also suffers from the black banding on dark images. The text is also not as sharp as the other device when looked at up close. The manufacturer date is July, 2021.

I'm currently not sure if this is due to a hardware difference of the display or from the software directly, but I won't be able to test what happens when I update the device with the issue until my bootloader unlock goes through as 12.5.1 is the latest for my current MIUI TR Region ROM and I need to region swap to Global ROM to get the latest as of now.

Thankfully as I've purchased it through Amazon, they're allowing refunds all the way to January 2022. I will be returning the device if the screen remains this way on the bad device, as I should definitely not have to put up with such an issue.
[Xiaomi Mi 11 Lite 4G] ckret:
You could check if both have same Display.

There is this how to from Mi Lite 5G:

Not sure how to explain it, you can try confirming if you have huaxing through the dial when you input the *#*#284#*#* which creates that bug file .zip. Unzip the file, there might be another zip file with the same name .zip, unzip that one too and open "dumpstate_board.txt" then try search "PANEL" if that is unsuccessful then try "K9A 36 02"

As far as I know all 4G have Tianma Display which will be displayed as K9A_36_02
[Xiaomi Mi 11 Lite 4G] Puremin0rez:
Thanks for the advice! I ended up using the ADB method to provide a full dump directly to my PC.

These are my findings:

Mi 11 Lite 4G that has crisp text and deep blacks: DisplayDxe: K9A 42 02 0b mp amoled dsc cmd

Mi 11 Lite 4G that has blurrier text and hazy tint: DisplayDxe: K9A 36 02 0a C0 amoled dsc cmd

It appears there is a hardware difference here. Looks like I'll be returning the one with the worse screen and hoping I get a better one with a reorder. If not, I'll look at a different phone entirely.

It's a shame that there's such a huge difference in the quality. It's unfortunately not something I'm willing to overlook, as a screen is something you look at every time the phone is used and I'd prefer my text to actually look nice and colors to be rendered correctly.
[Xiaomi Mi 11 Lite 4G] Denzki87:
I check my log bug file.zip and Damn! I got a crap display k9 36 02 0a C0 amoled
[Xiaomi Mi 11 Lite 4G] Puremin0rez:
Success! I ordered a replacement from Amazon and it has the DisplayDxe: K9A 42 02 0b mp amoled dsc cmd display panel. I knew it right away when I turned on the device, but had to do a bug report just to make sure :p

They also sent me the 8GB RAM version instead of the 6GB! Really lucked out.

Manufacturer date is September 2021 on the box, so it's quite new.

Darker colors (black, grey, etc) look great, there is zero banding or pixelation on dark videos or pictures, and text is nice and crisp.

So yes - just like the Mi 11 Lite 5G, the 4G also has two different types of panels.

DisplayDxe: K9A 36 02 0a C0 amoled dsc cmd is the worse panel

DisplayDxe: K9A 42 02 0b mp amoled dsc cmd is the better panel

For those of you with the worse panel, hopefully you've gotten used to it because honestly it's really not a truly horrible display, but when compared to the better display - it's definitely noticeable, at least with my eyes. I probably would have kept the device with the worse display if It wasn't for the fact that I had another one next to me with the better screen, which made me see the difference. The better screen should be preferred if you have the opportunity of playing the Xiaomi device roulette! :D
[Xiaomi Mi 11 Lite 4G] mvenezia00:
Do you know if the warranty cover black crush? I have DisplayDxe: K9A 36 02 0a C0 amoled dsc cmd. Maybe they Will replace It with a Better display?
[Xiaomi Mi 11 Lite 4G] asakurato:
You could try that, but you have no guarantee what display you will get when changing it.
[Android Q&A, Help & Troubleshooting] update.freak:
Hello all,

I have the following case.

I have a circular route as a GPX file. Now I am looking for an app in which I can import the circular route and which navigates me along this circular route.

It is important here that I do not want to start at the start (where the route was recorded), but at the "next entry point", so where I have the shortest way to the route from my location.

With Komoot this somehow does not work. Does anyone have a suggestion for an app.

Desirable would be additionally that the route I then drive (which ultimately corresponds to the specified route) is also recorded.

Thank you very much.
[Advantage X7500, MDA Ameo Upgrading] alcanaft:
Anyone have this Oficial WM6.1 Russia Rom for X7510

Thx For Your help Guys
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] ada12:
/*
* Your warranty is no longer valid, unless you lie.
*
* I am not responsible for bricked devices, strained relationships,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this kernel
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/

​

C.A.F 4.14 REBORN KERNEL​

​

This Kernel is designed for,

security

witch general improvement as possible .​

​

What is features included in this Kernel ?

​

​

driver stable from gram-q-oss debloated ( exept some drivers from mojito-r-oss... )​

latest CAF Kernel from LA.UM.9.1.1.r1-00700-RENNELL.QSSI12.0​

latest qcacld,fw-api,qca-wifi-host-cmn LA.UM.9.1.1.r1-00700-RENNELL.QSSI12.0​

latest Techpack audio LA.UM.9.1.1.r1-00700-RENNELL.QSSI12.0​

compiled witch AOSP Clang r433403b (13.0.3).​

Merged latest google common android-4.14-stable ( 4.14.258)​

*fixed error dts in log​

*ttl support for bypass some operator restriction​

*schedutil governor debloated​

*using pelt instead walt for EAS​

*zram lz4 as default / lz4 - lzo updated​

*added exfat support from mainline​

*latest f2fs from jaegeuk/f2fs-stable​

*wireguard drivers added​

*enable LTO clang​

*security features enabled - CFI clang enforced - selinux enforced by default​

*vdso32​

*TCP BBR as default , westwood​

*Backport TCP cubic​

*fixed support to report HVDCP_3P5 adapter​

​

and probably more check sources for more information about features and change ...​

​

Compatible Systems with this Kernel

​

​

This kernel is only compatible for Android 11 AOSP CUSTOM ROM.​

​

kernel version for GSI is only for phh GSI using stock vendor​

​

DOWNLOAD

VERSION AOSP ROM

​

​

DOWNLOAD

VERSION TREBLE

​

This Kernel will receive updates with new CAF tags and new upstream & improvement​

​

Guide Install :

​

​

Boot into recovery​

Flash the Kernel ZIP​

wipe dalvik-cache & Reboot to System- enjoy!​

​

BUG : kernel tested from curtana EEA no bug found actually . ​

-for report bug kernel only (issue rom, firmware issue ,mod flashed ex will be hardly ignored ) ​

-give dmesg/logcat to me and descript issue .​

​

Thanks for :

​

​

Xiaomi kernel sources​

Code Aurora forum for caf 4.14 release​

all other contributors no mentionned in sources​

​

XDA:DevDB Information​

C.A.F REBORN Kernel 4.14 for MI POCO M2 Pro,Redmi Note 9 S/Pro,Redmi Note 9 Pro Max​

​

Contributors :​

@ada12​

Source Code​

Status: Stable​
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] ada12:
14/12/2021

*upstream 4.14.258

*LA.UM.9.1.1.r1-00700-RENNELL.QSSI12.0

*various fix kernel by kerneltoast

11/12/2021

rebased kernel to :

latest CAF Kernel from LA.UM.9.1.r1-11400-SMxxx0.0

latest qcacld,fw-api,qca-wifi-host-cmn LA.UM.9.1.r1-11400-SMxxx0.0

latest Techpack audio LA.UM.9.1.r1-11400-SMxxx0.0

latest techpack data LA.UM.9.1.r1-11400-SMxxx0.0

Merged latest google common android-4.14-stable ( 4.14.257)

*latest exfat backport of namjaejon

*USB f_fs fix

*usb: fix undefined behavior caused by zero-length array

and more change see sources.
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] BladeRunnerA2C:
Damages hardware,

{Mod edit}
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] Oswald Boelcke:
@ada12 Thread closed. Please advise when the issue with the kernel has been fixed and the thread could be reopened.

Regards

Oswald Boelcke

Senior Moderator

P.S. Thread cleaned from outside-XDA items.

EDIT: @ada12 Thread has been reopened.
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] ada12:
I apologize for issue you have get . I have worked on it and fixed issue before post in xda do not be afraid . kernel is rebased.

regards
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] BladeRunnerA2C:
Well,

I can't risk my phone again on that, so I'll request you to drop the mess you did (which damaged the hardware), find a new way and walk around it,
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] ada12:
As I write it's fixed in sources

*And it's software issue it's no damage hardware reflash all firmware in edl resolve error created in fw.
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] Roberto Nigel:
Can you send me instruction on how to flash in edl?
[Redmi Note 9S / Note 9 Pro (Indian Model) ROMs, Ke] ada12:
guide for windows . ( solution for linux exist too but no tested in curtana )

You need drivers Qualcomm HS-USB QDLoader 9008 in your computer. { You can find easy by little search in internet }

For enter in edl mod easy method ( I assume for this method you have access to fastboot ) :

reboot to fastboot

* fastboot oem edl

Your device will then will go to black screen only. for verify Your computer reconize your phone now as QDloader 9008 in devices manager , you are in EDL mode.

*Open miflash tools

*Select your fastboot rom for curtana if you have this codename devices ... make sure

Flash it ... Wait ... Done reboot