yashsingh1/xdaforums huggingface dataset:
[OnePlus 10 Pro] Deviatorz:
I just installed global rom on the chinese pro 10 variant. However, when the phone is on standby (black screen) pressing the power button once has no effect. However a second short tap will bring up the power menu (on/off, restart, etc) instead of the password/PIN menu. I do not have facial unlock or fingerprint on.

Current the power button setting (Press and hold the power button) is on power menu. I have adjusted it already.

Any ideas? Thanks in advanced!
[OnePlus 10 Pro] dlads:
Recycle from assistant back to power menu.

Reboot between changes if this doesn't work.
[OnePlus 10 Pro] Deviatorz:
Just tried it and it didnt work.

Toggle --> assistant --> reset, then

Toggle --> power menu --> reset

FYI if the screen is off by not on standby (ie screen just turned off within a few seconds) the power button does not have this issue. its only when its in sleep mode (waiting after 1 min or so). I guessing this is just an issue with global rom on chinese phone variants?
[OnePlus 10 Pro] dlads:
If you've just updated from 12 to 13 and haven't wiped then I'd assume it's something to do with that.

This is the first im hearing of it, when I updated, the device automatically changed to assistant from power menu. So it may be related to the update.

I guess as well I would ask why you'd need the power menu if your phone's asleep.
[OnePlus 10 Pro] zopostyle:
Well another bug to the list...

I had to go back to Android 12 duo to other issues like wifi and apps not updating.
[OnePlus 10 Pro] Deviatorz:
I installed 13 from stock chinese firmware. I wiped through relocking the bootloader.

Power menu for when the phone needs to restart I guess? I mean I guess I don't need it but its good to have that function I guess....
[OnePlus 10 Pro] Deviatorz:
Yea I was hoping I wouldn't encounter any bugs.

I'm checking right now and it seems my apps are updating in google play, but I am doing this manually. not sure about background self updating (usually I have that off). Wifi seems to be working as well (even on my newly purchased route with wifi6).
[OnePlus 10 Pro] dlads:
Oh right.. No experience with the Chinese device or firmware, I'd say to rollback to the EU variant.. There's a thread for this in the guides section, just search or Google it and it'll link to a OnePlus community thread.

I don't have such issues on my device so change region and you should be fine.
[Xiaomi Mi 4] randomrepair:
Hello Guys, I have heard that we can install windows 10 mobile on Mi4 LTE but Is there any way to install it on Mi4W? Because both of the phones share the exact specification.

Thank You.
[Xiaomi Mi 4] xiaobuoluo:
No，the rom of mi4 was released by microsoft

but ms mobile was dismissed
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] TCBombLMG:
Wired & bluetooth headphones arent working on spotify.

Evolution X 7.2 alioth.

I have already tried turning of Hi-Fi in Mi Sound Enhancer, A clean flash of the newest version of Evolution X.

I listen to music everyday so if anyone could help or the devolpers see this plz help or plz fix this as soon as u can.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] cyanGalaxy:
I'm on Evo-X 7.2 and I encounter no such issues...

Are you in the Evo-X Telegram Group? You should join.

Which firmware do you use? 13.0.8 EU is the recommended firmware. Other users in the Telegram Group said that 13.0.4 works...
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] TCBombLMG:
Yes I've sorted it sorry I meant to close this post.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] cyanGalaxy:
I don't know if that's possible on XDA. But you can edit the title and put [CLOSED] before the title.

BTW, how did you fix it?

Other people reported to have the same issue, it would be nice if I could tell them a possible solution.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] TCBombLMG:
Uhh I updated the lastest firmware via twrp renamed the firmware zip file "update.zip" then I sideloaded it using adb and finally I just did a clean reflashed of Evolution X

Downloaded from here https://xiaomifirmwareupdater.com/firmware/alioth/stable/V13.0.8.0.SKHEUXM/ a link I got from the official telegram
[Samsung Galaxy Tab A7 Lite] decentdude:
I have a Samsung galaxy tab A7 Lite T225XXU1AUL1, its KG status is broken. My tab has Knox security, I can't use it because it shows can't create a work profile. I am also not able to enable the developer's options on my Tab. I clicked on the build number many times but nothing happened. Please help me to fix my Tab.

Thank you in advance.
[Samsung Galaxy Tab A7 Lite] tom.android:
xxxx
[Samsung Galaxy S21 Ultra] musakamis:
There is no root on my phone, but knox has been triggered before, does anyone have any thoughts on how I can use the current version of Samsung health on my non-rooted phone?
[Samsung Galaxy S21 Ultra] ShaDisNX255:
I can only think installing the patched Samsung Health app which you can find here:

SamsungAppsPatcher - Adil Hanney

Samsung Apps Patcher for Samsung phones with custom ROMs.

adil.hanney.org

But the owner of this website no longer has a Samsung phone and I assume its already outdated. Other than that, no, I don't think you'll be able to get it fixed without root.
[Samsung Galaxy A02s] gigge:
Hello, as we all know, it is not possible to record calls anymore on Samsung mobile phones.

But I have read that by changing the CSC it should be possible to record calls.

I Own one SM-A025G with the following CSC

Reading list CSC...OK

3IE | AMO | ATL | ATO | AUT | BGL | BOG | BTU | CNX | COA | COS | CPW | CRO | DBT | DTM | EUR | EUX | EUY | FTM | H3G | HUI | ITV | LUX | MAX | MBM | MET | MOT | MSR | NEE | O2C | O2U | OMN | OPV | ORO | ORS | ORX | PHE | PHN | PLS | PRT | ROM | SEB | SEE | SIM | SIO | SWC | TCL | TIM | TMH | TMS | TMZ | TOP | TPH | TPL | TSI | VD2 | VDC | VDI | VGR | VIP | XEF | XEH | XEO | XEZ

(from SamFw_Tool_v3.3.1)

Is it one of the CSCs with which it is possible to activate call recording?

Have only found SEK CSC for SM-A025F, but cannot be flashed in the mobile?

(but identical hardware?)

Problem with BT.

Wireless headphones do not work during calls !!

Airpods or skullcandy and two different varieties of cheap bt headphones have been tried, can only hear voice but they can't hear me talking during calls.

Music works well.

Slightly better when changing BT codecs. But the quality of voice calls is poor. unusable solution.

It is not possible to turn off "Disable Bluetooth A2DP Hardware Offload" it is grayed out in dev options. Something that is recommended in the forum otherwise.

Any help or answer is appreciated!
[OnePlus Nord Questions & Answers] sixtenson1:
I tried to install LineageOS on my OnePlus Nord following this thread:

https://xdaforums.com/t/rom-12-1-unofficial-lineageos-19-1-microg-oneplus-nord-avicii.4329631/

I successfully flashed the recovery.img (provided in the thread), and did a factory reset in recovery. However, I could not find the "Apply Update / Apply from ADB" option, so I though I'll just flash TWRP on there instead. But this bricked my phone. And I got this error message:

View attachment 5732667

If I hold vol-down + power button I was also able to reach fastboot mode.

View attachment 5732669

I found MSMDownloadTool and this thread:

[OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS

Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...

xdaforums.com

But whatever Firmware image I tried to use the result was always the same: "Device not match image".

(On the box that the phone came in it says "OnePlus Nord AC2003")

I tried different versions of Global, EU and India Firmware files.

I have also tried different versions of Qualcomm drivers (1.00.25 and 1.00.55)

And I have tried different cables, and USB ports.

So I tried to flash stock ROM using this thread:

https://xdaforums.com/t/rom-stock-fastboot-opn-stock-fastboot-roms-for-oneplus-nord.4142153/

It works fine in the beginning, but after the fastboot reboot fastboot step I start getting:

FAILED: Flashing is not allowed for Critical Partitions.

Also, If I do fastboot flashing unlock_critical it says the phone is already unlocked.

I have also tried fastboot boot recovery.img with different .img files (recovery.img provided in the first thread I linked, and also TWRP.img) but this just reboots the phone, and then it gets stuck at Oneplus logo reading "Fastboot Mode" below, until I restart and it gets into fastboot menu again.

I can only reach fastboot mode as shown in picture above, and EDL mode.

I have no clue on how to fix my phone. Any ideas?
[OnePlus Nord Questions & Answers] sinkoo1979:
Change slots and try again. Had the same problem. now using pronton lock off rom A13. Make sure you are on android 10 or 11. Hope this helps
[OnePlus Nord Questions & Answers] sixtenson1:
Thanks a lot for your reply!

You'r reply helps a great deal in getting my faded hope back! However, I am kind of new to all this, so I have a few questions.

What do you mean by change slots?

What is pronton lock off rom A13? Is it something I should use as well?

How would I make sure that I'm on android 10 or 11? Do you mean the Android version file for MSMDownloadTool? Or stock ROM to try and fastboot flash with? Or do you mean the android version that was installed on my phone when it got bricked?

Thanks in advance!
[OnePlus Nord Questions & Answers] sinkoo1979:
fastboot --set-active=a. A or B will be the partition. Check which partition you are on first on fastboot.

Custom Rom

Don't know which android version you have

Use this link https://xdaforums.com/t/rom-stock-fastboot-opn-stock-fastboot-roms-for-oneplus-nord.4142153/
[OnePlus Nord Questions & Answers] sixtenson1:
Thanks for the additional information!

I started by checking what slot was in use:

fastboot getvar all

(bootloader) current-slot:a

I then changed slot to b:

fastboot --set-active=b

And then started following the link you provided.

However, running in to the same problem as before.

When running:

fastboot reboot fastboot

I get the following Error:

Rebooting into fastboot OKAY [ 0.002s]

< waiting for any device >

fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.

And when trying to flash abl:

Sending 'abl' (1996 KB) OKAY [ 0.055s]

Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.

')

fastboot: error: Command failed

fastboot flashing unlock

fastboot flashing unlock_critical

both generate the same Error message:

FAILED (remote: ' Device already : unlocked!')

fastboot: error: Command failed

What could this be?

Thanks in advance!
[OnePlus Nord Questions & Answers] sinkoo1979:
Mine worked with that. Don't really know now. Hope you solve it.
[OnePlus Nord Questions & Answers] sixtenson1:
When I run:

$ fastboot oem device-info

I get the following:

(bootloader) Verity mode: true

(bootloader) Device unlocked: true

(bootloader) Device critical unlocked: false

(bootloader) Charger screen enabled: true

OKAY [ 0.001s]

Device does not seem to be critical unlocked. When I run:

$ fastboot flashing unlock_critical

Output is:

FAILED (remote: ' Device already : unlocked!')

fastboot: error: Command failed

Does the device need to be critical unlocked? And if so, how can I unlock it?
[OnePlus Nord Questions & Answers] unbrickmee:
I have noticed we have the same issue, easy fix !

I fixed it by following this simple guide -

* first step is to download the ROM file with the MsmDownloadTool V4.0(only PC).

* download the QUALCOMM driver(link in the YouTube video description).

* turn your phone off by pressing the power button and the + volume.

* when phone is turned off- press both volume buttons for 10 sec

* connect an original usb cable to your phone and to the 3.0 port on your pc.

* now the device should be recognized in the "device manager" as an qualcom hs-usb qdloader(com4)

* open msm tool and look if the device is recognized (COM4)

* if it is recognized change target to india and click start.

* when it finished it will automatically reboot phone, mine whent staright to recovery mode, but i just pressed reboot and it started correctly (:

feel free to ask any questions, I know how frustrating it could be.

device used- one plus nord ac2003

ROM + MSM TOOL VERSION- avicii_14_I.13_210204
[OnePlus Nord Questions & Answers] sixtenson1:
Thanks a lot for your answer!

I followed every of your steps, but I get the same result as I describe in the original post.

In MSMDownloadTool, in the "Status of Last Communication" column it says, in red:

"Device not match image".

Any idea how to fix this?
[OnePlus Nord Questions & Answers] gorro8:
Try to reinstall correct drivers
[General Questions and Answers] waleeed:
hi i have profitable app idea i would like one to contact me
[Xiaomi Mi Pad 5 Pro] rodriarevalo:
Good morning

I bought a Mi Pad 5 Pro Wifi version (without 5g) by ebay and it arrived with the bootloader unlocked and a global rom with my language (Spanish). I know it is not an official rom from Xiaomi. The problem is that it does not support OTA updates.

I would like to find some help about where I can find roms like the global one I have and instructions to flash it, or instructions to flash the CN version if needed, or Lineage OS .

Thank you very much for your help.
[Xiaomi Mi Pad 5 Pro] siamese007:
@radriarevlo Try this ROM. My device is Mi Pad 5 Pro 5G. I've flashed GSI ROMs but got many problems with hardware. So it's best for now to stick with Stock ROM which is CN version. With CN stock ROMs, I can still read and write in my local language by using Gboard. But the UI can be only Enlish or Chinese. No worry about Google Play Store. You can install it easily with GetApps that comes with the stock ROMs.
[OnePlus 8T Questions & Answers] FreeDee:
Hi, I did something stupid and need some help please.

I got the bootloader unlock code for my KB2007 - Unlock went well, no issues.

Then I proceeded to download and install the latest official TWRP - Also no issues, I was in the custom recovery, created some backups etc.

After that, I followed the instructions to install Lineage OS as posted here:

Install LineageOS on kebab | LineageOS Wiki

wiki.lineageos.org

I flashed the dtbo and vbmeta partitions as instructed and proceeded with adb sideloading the copy-partitions-20220613-signed.zip file - Somewhere around here is where things went south.

I was not able to access/read my data partition anymore, and attempted to flash the lineage-recovery. After a reboot, I'm now stuck in the bootloader (fastboot). When I select Recovery mode, the phone just goes black. I also can no longer "fastboot boot twrp.img" - Error: "Failed to load/authenticate boot image: Load Error".

After checking the guide one more time I noticed it says the device has to be on Android 12, which mine was not (it was still in factory condition - Android 11). So that was likely the problem.

So now the big question is can I recover from this state? If yes, what's the best way to do so?

Thanks so much!
[OnePlus 8T Questions & Answers] Rootk1t:
Restore to stock via MSM.
[OnePlus 8T Questions & Answers] IAAxl:
You must update to OxygenOS 12 before installing lineageos 19.1 or you will brick.

The lineagsos guide is wrong and I bricked my device by following it too.

For now, you can only unbrick it with msmtool.

[OP8T][OOS TMO KB09CB] Unbrick tool to restore your device to OxygenOS

Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...

xdaforums.com

Then OTA to OOS 12, then install LOS19.1.
[OnePlus 8T Questions & Answers] FreeDee:
Thanks guys! I was able to restore the device using the MSM tool 👍

I intend to keep it on OOS 11 (and potentially flash LOS18.1), because KB2007 is the T-Mobile variant and based on what I read dual sim only works with OOS 11.

The problem is it is becoming increasingly difficult to find instructions (or even downloads) for anything but the very latest versions :/
[OnePlus 8T Questions & Answers] Rootk1t:
You can also use KB2007 OOS 13 beta 1 which works with dual sims.
[OnePlus 8T Questions & Answers] FreeDee:
Thanks! Yeah, I also read about that, and it does indeed sound like a potential way to go.

Do you know if anyone has figured out yet what makes this "beta 1" special in that it allows dual sims? I think I also read it's no longer possible with beta 2.
[OnePlus 8T Questions & Answers] Rootk1t:
As far as i know, it's still unknown what makes beta 1 work in dual-sim mode.
[Android Stick & Console AMLogic based Computers] stoyanov_v:
Hello! My X 96mini smelled burnt. I took the board out and saw that one component had burned out? Can you help me figure out what it is so I can replace it? I am attaching a photo!

Thanks!
[Android Stick & Console AMLogic based Computers] stoyanov_v:
Replace it with APS2415-ADJ - work fine
[Samsung Galaxy S21 Ultra] dikime:
New update to topic:

I decided to repair the software of my Galaxy S21 (Exynos) by flashing official firmware from Samfirmware, same version as I was running. It was in a bootloop before, so there was nothing esle to do. Phone was rooted with magisk, stock recovery.

I found what my firmware is from the recovery, found the exact same file, with the correct CSC.

Downloaded that firmware from Samfirmware, downloaded patched Odin from XDA.

Added, flashed, used HOME_CSC in order to preserve my data.

Reboot and immediately before I even get the boot logo or the charging animation, I get this error:

This is ENG binary Please Use USER binary

Allegedly this is what happens when you flash an engineering build, not an official one. But how? I downloaded and flashed official stuff? It's the exact same version my phone is already running. Where did I go wrong and how can I fix that?

I've attached the Download screen of my phone.

Thanks!

Old news:
[Samsung Galaxy S21 Ultra] palamosteliaro:
Flashing TWRP = having to delete data (to be able to access the internal storage)

I am pretty sure (wait for confirmation before doing it) that if you flash the HOME_CSC file instead of the CSC on Odin it keeps your data.

This is why we need to vote with our wallets and buy phones with sd cards. I dont really care, because I never keep anything important on my phone, but I feel for you buddy.

EDIT: from here: https://www.droidviews.com/difference-between-csc-and-home_csc-samsung-firmware/

CSC – If you flash the CSC file, it’ll perform a factory reset of your Galaxy device and wipe all data while installing a new firmware to bring your device to the same state as it was when you purchased it. Go with CSC if you want a clean installation.

HOME_CSC – On the other hand, if you want to keep your Samsung phone’s data and settings even flashing the stock firmware, you can select the HOME_CSC file.

At your own risk, pls dont blame me if it doesnt work!
[Samsung Galaxy S21 Ultra] GeeAyeZee:
Flash a patched vbmeta again
[Samsung Galaxy S21 Ultra] dikime:
Hi, what do you mean? Flash both TWRP and vbmeta, as if I'm doing it for the first time?

I think the phone was already decrypted while following the Magisk root tutorial, so these two steps should be the only thing necessary for the phone to boot to TWRP, right? I know how to rescue everything once I'm in there.
[Samsung Galaxy S21 Ultra] shaharofir:
Try entering safe mode and disable all magisk modules:

Power on your Galaxy phone or tablet in Safe mode

We’ll walk you through how to start your Samsung Galaxy phone or tablet in Safe mode. This mode prevents third-party apps from running on your device.

www.samsung.com

You can access adb when on recovery mode or download mode so you can also enter safe mode via one of these commands:

setprop persist.sys.safemode 1

or

echo "1" > /data/property/persist.sys.safemode
[Samsung Galaxy S21 Ultra] GeeAyeZee:
Flash the vbmeta file in odin
[Samsung Galaxy S21 Ultra] dikime:
The phone auto-enters safe mode after a few bootloops, so I guess that's beat. When the phone is in stock recovery, doing any adb commands tells me the device is recognized, but "unauthorized".
[Samsung Galaxy S21 Ultra] shaharofir:
So you can enter download mode and flash stock (just super)
[Samsung Galaxy S21 Ultra] Muledeer:
You gonna have to get authorized again. Check youtube for help. I had that issue a couple months ago. Think it had to delete the android folder and reinstall adb
[Samsung Galaxy S21 Ultra] dikime:
Alright, decided to flash stock firmware with Odin. Found my files from Samfirmware, and since I want to keep my data, flashed HOME_CSC. Now the phone won't boot at all, giving the error:

This is ENG binary, please use USER

Now why did this happen and can I do anything to change that? I would really like to not flash CSC and wipe my phone, but it's looking more and more likely.

I used the patched 3.14.1 Odin, could that be the issue? Shouldn't matter.

The Download mode screen says:
[Samsung Galaxy S21 FE] szerwony:
Hi. Yesterday I got new S21 FE 5G and I have problem with gesture typing. As you can see in the video below, when I try to type longer words with fast finger slide, the keyboard often "loses" my move and starts a second one, resulting in typing two different words, instead of one. Tested on a Samsung and Gboard keyboard. I have found many threads across the internet about this problem on S22, but they say it was fixed in June by software update. Now we have October and this issue exist on my S21 Fe. Any ideas on how this can be fixed?
[Samsung Galaxy S21 FE] Chorne:
Same here. I tried both keyboards too. It is the worst phone I have ever owned. I can't believe a high-end phone has such problems and such a bad camera.
[Samsung Galaxy S21 FE] szerwony:
Some people on Reddit say that this problem appeared since September update, but I can't confirm this as I bought phone this week. That's why I am wondering if it is damaged touchscreen and I should return phone or just wait for update.
[Samsung Galaxy S21 FE] coolawy:
I have the same. And it started 2 updates ago.
[Samsung Galaxy S21 FE] coolawy:
View attachment 5734177
[Samsung Galaxy S21 FE] Randi03:
I noticed there is a new update CVI5 (snapdragon). I installed it and I can swipe type with no error. However I am not used to doing this and I am a bit slow at it so I cannot recreate this issue. Maybe you can test after this update and let us know if it's fine now.
[Samsung Galaxy S21 FE] szerwony:
I have this update since wednesday, it didn't change anything for me.
[Samsung Galaxy S21 FE] MemurBey:
I have this problem sometimes after the update

I was thinking it due to my new screen protector

I hope someone can port a pixel rom to this device
[Samsung Galaxy S21 FE] jbs68:
Hey

I also have the same problem!!!

And yes, I confirm that I've only had the problem for a few months (after a system update....)

it's very annoying, I slide very fast on the keys and, it takes a lot of time to check and correct the texts entered...... :mad::mad::mad:

And i confirm that I already installed the latest firmware (CIV5....)
[Samsung Galaxy S21 FE] GymPanse:
Hello. I have the same problem. I bought the phone 2 weeks ago and was immediately offered an update. After that I have the same problem with every keyboard. Has anyone contacted support yet?
[Samsung Galaxy S21 FE] GymPanse:
@coolawy may I copy your picture and post it in the German Samsung forum? I'm making a post about the problem.
[Samsung Galaxy S21 FE] coolawy:
Sure, go ahead
[Samsung Galaxy S21 FE] jbs68:
@GymPanse , any news from the German Samsung forum?

This problem is really starting to annoy me :mad::mad::mad:

Thank you !

Edit:

I also opened a post on the French Samsung forum.... @coolawy , I also copied your screenshot, thx
[Samsung Galaxy S21 FE] GymPanse:
So far I only got the tip to reset the settings of the Samsung keyboard to the default setting. Of course it didn't help.

Then I should send a bug report through the Members App. I did, but haven't gotten a response yet.