yashsingh1/xdaforums huggingface dataset:
[LG G5 Questions & Answers] oliverjames:
After review of the many comments related to this problem, I believe that I've found the solution; at least this has worked for me.

The problem does seem to be due to bad electrical contacts. I believe that the 10 small rectangular contacts seen on the attached picture of a replacement start button / fingerprint sensor are not making good contact with their respective electrodes on the motherboard.

My solution is to cut a piece of plane paper (I used 90gm/m2 printer paper) in an L shape to fit behind these. Note there is a small rectangular projection (chip?) to avoid but otherwise the surface is adhesive and so securing the paper pad is fairly easy.

With this spacer the contact is now good and the button now works to start and stop the phone. Hopefully the fingerprint sensor may now work. I'll post an update when I've tested that.

This phone works well but has the design fault that allows the phone back to bend, for example due to a bulging battery, which breaks the contact. View attachment 6116160
[Samsung Galaxy A53 5G] thlr:
or maybe just root, i'm kinda new to all this and i wanna get a custom os cause my phone is slow, but every major custom os (lineage, EvoX, grapheneOS) says that it doesn't support the A53 yet. although I've seen some people having these "unsupported" roms.

I'd appreciate it a lot if someone just explained to me how all this works.
[Samsung Galaxy A53 5G] mytja:
https://github.com/phhusson/treble_experimentations/wiki/Samsung-Galaxy-A53-5G and

Generic System Image (GSI) list

Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.

github.com
[Samsung Galaxy A53 5G] rabaimor:
Grapheneos doesnt have good performance, it focuses more on security. I recommend a lineageos gsi without gapps. I use it as well, it had better performance and significanly better internet connectivity than stock oneui.
[Samsung Galaxy A53 5G] akasuoo:
Any tutorial for how to install it? I get only bootloops and need to reflash rooted stock. I have twrp and orange recovery on my sd card. Pls help me somehow. Ty
[Samsung Galaxy A53 5G] rabaimor:
Here you go:

Download from here:

Andy Yan's personal builds // GSI - Browse Files at SourceForge.net

sourceforge.net

You want the "td" versions instead of the light for less issues and better performance (I've tested both).

Step 1

Download bvN version for vanilla

bgN if you want gapps (yuck)

Step 2

Move and extract system image to your sd card.

Step 3

do a backup in orangefox so you can go back if you mess up something

Step 5 flash the system image from your sdcard to the system partition.

Step 6 wipe and format all data (even if you can boot without doing this it will cause a bunch of issues)

Step 7 flash afaneh kernel if you arent using it already

Step 8 Flash magisk.apk if you want root
[Samsung Galaxy A53 5G] oslavq:
Hi, i am new to this, can you explain what is afaneh kernet? And why do i need it?
[Samsung Galaxy A53 5G] rabaimor:
Its this ported to the a53:

GitHub - osm0sis/AnyKernel3: AnyKernel, Evolved

AnyKernel, Evolved. Contribute to osm0sis/AnyKernel3 development by creating an account on GitHub.

github.com

They explain it on the github better than I could so just check that out if your interested in it.
[OnePlus 9] middlestream:
Hello to all the intelligent and benevolent people who answer questions for noobs like me, I truly appreciate you.

I'm trying to use the MSM tool to update to Stock android 13 in preparation for lineage OS as per their instructions (upgrading from lineage 18).

I familiarized myself with this thread https://xdaforums.com/t/global-oneplus-9-msm-tool-updated.4284779/ and a few others that discuss the process, and I can't find a good drivers link.

I saw someone mention "qualcomm hs-usb qdloader 9008", so I tried these drivers https://qdloader9008.com/, and although this does seem to show in device manager...⬇️

View attachment 6090023

...it doesn't show in the MSM tool ⬇️

View attachment 6090024

To give a general idea of my goal, I plan to end up on lineage 20 (instead of 21) for stability reasons, especially since I usually add magisk, lsposed, substratum. I believe I may be able to just flash lineage and hope for the best, but I prefer to do it the right way, and from what I understand upgrading to stock android 13 has vendor updates like bluetooth and modem. Feel free to comment on or ridicule this convoluted plan of mine :-D
[OnePlus 9] middlestream:
UPDATE: I believe I got the drivers to work (using this guide https://droidwin.com/yellow-exclamation-next-to-qualcomm-hs-usb-qdloader-9008-fix/), but I am now getting the error "Device not match image" on the MSM tool.

I have LE2115, which I thought is the global version, but it seems it is actually the US unlocked version, which has no corresponding image on the onepluscommunityserver.

I will continue to read and research, but if anyone can give me some pointers I would appreciate.
[OnePlus 9] xlinux_:
Uninstall the driver that shows up in device manager, go to OnePlus's website and download the driver for your device, actually look for the OnePlus 9 drivers not universal. Make sure to reboot PC before attempting to install anything,. Do not download hs USB qdloader 9008 from unknown sources it may contain viruses. Only download from OnePlus website!!.

Once that is sorted, your device is the GLOBAL variant. Not US if it's le2110 or le2115 it's a Global variant which means only use MSM tool for the global variant if you need any more guidance please feel free to reply in detail of the issues.
[OnePlus 9] middlestream:
That makes sense. I ended up using the multi target MSM tool from THIS guide which worked to get me on global OOS 11.

OTA did NOT work, but I used the stickied repo thread (HERE) to download newer versions of OOS 11 and incrementally began to apply manual local updates, and after the first few times (still on android 11), the OTA suddenly worked perfectly, and updated me straight to 13, and then again to latest OOS 14.

I have decided to stick with stock ROM for now, and I am happy with how things look so far, but I am concerned that OTA updated me straight from 11 to 13. Was that supposed to happen? Did I miss out on vendor updates?

I am also concerned with the custom MSM that I started with. Apparently it was bundled with a modified version of fastboot, as he explains in that guide, and I'm not sure how that may affect me.

Any more tips would be greatly appreciated.
[OnePlus 9] middlestream:
oops, forgot to hit reply in my response and not sure how to tag you. see above please.
[OnePlus 9] xlinux_:
All good 💯% glad you could fix your device!!!, I don't think it's of any concern if you managed to update correctly anything that was flashed previously is long gone!

OOS14 isn't to bad I just didn't like the OS.

If you want to move to custom ROMs get familiar with firmware flashers provided by some developers, some developers will build the rom with the firmware already installed so only need to flash via adb sideload, or recovery like twrp it depends on what the developers have provided, also to mention if you get stuck with anything the xda community is always here to help.

Make sure to read through Lineage Os wiki as then can give you some tips on the steps required for flashing devices.

https://wiki.lineageos.org/devices/lemonade/
[OnePlus 9] middlestream:
Thanks for the reassurance! My next step is installing TWRP and rooting with magisk, let me know if you know of any updated guides, most of what I'm finding is from 2021.
[OnePlus 9] xlinux_:
YOU WILL need platform tools for any modifications:

Just make sure your bootloader is unlocked via fastboot OEM unlock it will wipe any data after it's been unlocked...

you do not need a token for OnePlus devices.

Fastboot instructions from linage: https://wiki.lineageos.org/adb_fastboot_guide

You don't need to do this method:

,download android studio from the official website for android developers and install the SDK platform tools for adb and fastboot. https://developer.android.com/studio

This method is preferred by most users:

You can install the required files inside of android studio

Or directly download the SDK platform tools

https://developer.android.com/tools/releases/platform-tools

to use platform tools without using android studios method and using the direct tools that the second link provides ,,

you need to extract the zip and place it on your drive somewhere inside of windows providing that you are indeed using windows, my preferred method is to install the SDK Platform tools from android studio inside the application there is a tool to download and install the platform tools and drivers required

If android studio method :: you don't need to define the path each time you start a CMD line session:

To define the path so CMD can mount the correct tools

In CMD line::

("cd" mounts the location of the tools)

(path to platform tools for example on the desktop)

cd C: \users\username\desktop\platform-tools

This would mount the path to the location of your tools in Command prompt which then anything you flash will have to be in the same directory /folder as platform tools this is the much easier method.

As for directly installing the android studio and installing the tools from inside the application which then you don't have to define the path to your tools but only to the files you're going to flash.

You're probably familiar with fastboot if you can navigate msmtool I will leave these instructions here incase anyone else needs help..

There is plenty of info on the internet also, I just felt like explaining this no need to follow my instructions. 👍
[OnePlus 9] middlestream:
@xlinux_ WOW such good material. You are right I am familiar with some of it, but still very useful as a reference.

I'll be working some more on it tomorrow and I will likely continue to ask you questions for as long as you are willing to share your knowledge.
[OnePlus 9] shadabkiani:
If you plan on flashing LineageOS, you don't have to worry about being on a specific firmware, because LinegeOS's ROM zip contains the required firmware images. Generally it is recommended to just update your phone to the latest offical firmware.

Also, you don't need TWRP to flash LineageOS or root with Magisk. You can use adb sideload feature from LinegeOS recovery. But if you do want TWRP, you can have it. Just remember that OnePlus 9 (and most phones after that) don't have dedicated /recovery partition anymore. The recovery resides inside boot.img. That's why you would notice that TWRP isn't flashed from fastboot (no fastboot flash recovery whatever.img). Instead it is TEMPORARILY booted from fastboot (fastboot boot whatever.img). And then you flash TWRP from inside TWRP once booted which patches your boot.img.
[OnePlus 9] middlestream:
@xlinux_ So I installed twrp using fastboot and THIS unofficial build, now trying to root with Magisk. Apparently the old method is no longer recommended (rename apk to zip and flash directly from twrp) and I believe one reason for that is to allow for future OOS updates, which is important for me.

However learning the new method (patching boot) is taking some time, any more tips would be appreciated.
[OnePlus 9] shadabkiani:
If you flash from TWRP, you don't have to rename apk to zip. The apk is visible from flashing options.

Another method is to adb sideload Magisk.apk from LineageOS recovery (or whatever custom ROM you are on) but you are on TWRP.

Patching boot.img is simple. Have your stock boot.img (I mean if you are on LinegeOS, then its boot.img from ROM zip file). Install Magisk app. From Magisk app, click install and choose patch image. Slect your boot.img. Magisk will patch and create a new patched boot.img in Download folder. Copy that to PC. Reboot phone to bootloader. Temporarily boot this patched image by command fastboot boot patched_boot.img. Phone will boot up. Open Magisk app (if it asks for additional setup, ignore it, it doesn't work). Click Install and choose Direct Install. This will now root your phone.
[OnePlus 9] middlestream:
@shadabkiani Hey thanks for all that!

Firstly if you're right then that whole lineage thing is so annoying, not only do they warn multiple times about starting from the correct firmware, but they also have a dedicated page for directly updating the firmware, which seems useless if it's bundled with the ROM.

But anyways once I ended up on OOS 14 I decided to stay.

And thanks for explaining that twrp is in boot, that makes a lot of sense.

I'm wondering if you know how this might affect root and magisk installation. I believe the purpose of doing it using the official method of patching boot is using a process that backs up the original boot image for future updates. But did I already ruin it by installing twrp to boot? Am I wrong about the purpose of using that method?

I'm familiarizing myself with your instructions now.

EDIT: I'm realizing now that OOS 14 is the final feature update for OP9, so maybe I shouldn't be driving myself crazy just to arrange for a few future security updates. Then again, perhaps future updates will have bug fixes as well? OOS 14 is still pretty new and I've seen many complain about bugs.
[OnePlus 9] xlinux_:
OOS14 has many bugs..

Magisk is typically not installed via an APK file since it's a systemless root solution. Instead you need to flash via patched boot.img don't download anyone elses boot.img if they provide you one. Only use your own boot.img for your rom, which you will have to extract it.
[OnePlus 9] shadabkiani:
That LineageOS guide was written when LineageOS ROM zips didn't have firmware included. Along the lines, I think it was midway LineageOS 20 that the builds started coming with required firmware included. You can also verify this by downloading latest ROM zip and extract payload.bin from zip, and then further extracting that payload.bin using Payload Dumper Go. You will find firmware images there as well (all the ones that they asked you to flash in the guide link you shared). They should at least put a note on top of guide that these steps are not needed anymore for latest builds.

Secondly, since you flashed TWRP permanently, that means your boot.img is modified now. Whenever there is an OTA update, although it will show it's available, but it will fail installation because of boot.img modified. You should have backed up original boot.img first (using MSM Tool's readback feature). That is the whole reason why it's recommended to root with temporarily booting the Magisk_patched_boot.img and then using Direct Install from Magisk app in order to gain permenent root. That way, Magisk will back up stock boot.img which you can restore later from Magisk app. If you flash patched boot.img directly from bootloader, you will gain permanent root, but original boot.img will not be backed up by Magisk. If you have original boot.img backed up separately, that would be fine too and you can just flash back your original boot.img and proceed with OTA.

Now I don't know if you can just uninstall TWRP and your boot.img would be considered reverted back to stock condition or not. Let's see when the OTA comes and try that.

By the way, all this hassle of backing up stock boot.img in order for OTA to work is not required for custom ROMs OTA. Their OTAs work fine, so you can just have TWRP permanently flashed (I don't think there is any need for that btw; I don't keep TWRP) or directly root by adb sideload Magisk.apk from recovery. However after OTA, you still have to reflash TWRP and/or Magisk.
[OnePlus 9] middlestream:
@shadabkiani Awesome breakdown, makes a lot of sense. I was not aware of MSMs readback feature but it seems obvious now.

I was trying to figure out how to get ahold of my boot image for magisk patch, is that how I was supposed to do it? Or can I just use twrp to grab it at this point?

You mentioned possibly uninstalling TWRP later as my only option for future OTA, but I do still have the OOS 14 update file from Oxygen Updater app, any chance I can grab a clean boot.img there, or am I misunderstanding what update files really contain?

And how the heck do you survive without TWRP or some sort of nandroid capability?? Every time I do something stupid like playing with lsposed or substratum I take a nandroid for emergencies. Would you use the MSM tool for that? What about devices without it? If there's a better way for someone like me addicted to running crazy experiments on their daily driver please teach me your knowledge :LOL:

PS you're totally right about custom ROM being better for updates, but lineage seemed so plain as compared to all these exciting new features specific to OOS, plus I need to try stock every few years in order to prove to myself that custom ROMS are worth it :cool:
[OnePlus 9] xlinux_:
If you download the original ota from the pinned thread in the 9 forums you can extract the payload.bin inside the zip with either terminal emulator, or on your PC Payload dumper go, there is a reference in one of the threads on xda,

https://xdaforums.com/t/tool-a-quick-android-ota-payload-dumper.4173271/
[OnePlus 9] shadabkiani:
In order to extract boot.img from OTA update file using Payload Dumper Go, it has to be full OTA, not incremental. LE2115 doesn't have OOS14 full OTA; it's incremental. Last full OTA was OOS13 593 I guess (check the sticky thread Oxygen OS Repo; they only upload full OTAs). You can also see that from Oxygen Updater app.

I don't have TWRP permanently flashed. If I ever need it for some reason, I just temporarily boot it and use it for whatever reason and then just reboot phone. If you backup your boot.img now (using TWRP or MSM Tool's Readback feature) it will be with TWRP patch. You can use that for Magisk patch (although I haven't done it this way before but it should work), but OTA will not proceed unless stock untouched boot.img is restored.
[OnePlus 9] shadabkiani:
Try MatrixX ROM. It is very exciting with tons of customizations. It has stock OOS cam as well. And it is rooted with KernelSU. You just install KernelSU app and grant root permission to whichever app you want. The rest of the system wouldn't know you are rooted. So Play Integrity passes by default. Unlike Magisk where you have to hide the root and do other workarounds.

The ROM's thread is in OnePlus 9 Pro forum, but builds (and separate firmware flasher) is also available for regular OnePlus 9 too.
[Xiaomi Poco X6 Pro / Redmi K70E] drno744:
Hello, a question after the update of my phone, unfortunately I can no longer access the engineering mode. Previously it worked with the key combination in question, unfortunately this is no longer possible after the update. When I look in the system apps, the app is MDK not active. Can this help?

Regards drno
[Xiaomi Poco X6 Pro / Redmi K70E] ApexPrime:
*#*#3646633#*#*

Does this work for you? If not, search for mediatek engineering tool on playstore and try that
[Xiaomi Poco X6 Pro / Redmi K70E] drno744:
Hello, No, Code Not Work, engineering Mode in Playstore Not Work on my Phone. And the installed MTK App sleep.View attachment 6090601
[Xiaomi Poco X6 Pro / Redmi K70E] PNTRATOR:
This work for me, I'm on hyperos 1.0.8.0 global
[Xiaomi Poco X6 Pro / Redmi K70E] drno744:
Hello, the apps no support the poco x6 pro.

Best regards
[Xiaomi Poco X6 Pro / Redmi K70E] ApexPrime:
Hello, recently i was checking out the engineering mode on my phone and i opened a setting just to see whats inside but i didnt change anything. When i closed the app, there was a persistent notification which wasnt going away so i force closed the app. Now the code to access engineer mode has stopped working. I have restarted the phone and cleared the app data as well but it still wont open. If anyone knows a way to force start the app please let me know. Otherwise, just take this as a precaution and never force close the app.
[Samsung Galaxy Z Fold 5] Xeon:
Anybody noticed a remarkable battery drain after updating to oneui6.1 ? Mine is definitely worse and the phone isn't making it till the end of the day anymore. I used to have 8-9 hrs SOT before the update but now it's less than 5hrs.

I did an upgrade not fresh installation so not sure about your observations.
[Samsung Galaxy Z Fold 5] inthedark22:
Me too. 3 hrs sot. 28 percent left. Did format cache too. I hope it settles.
[Samsung Galaxy Z Fold 5] stavrone07:
Same here! Noticeable battery life decrease.

On OneUI 6.0 and 5.1.1 it could last 2 workdays with 3-4h SOT in sum. On 6.1 it reduced to 1,5 day with 2,5-3h of usage. Still not bad comparing to S23 users who complains a lot about battery life.

I think that fresh install should solve all kind of problems as I see many people noticed better battery life after update even through OTA.

BTW, overnight discharging has increased too. I have a power-saving routine overnight and it was 2-3% overnight and now it's 5-6% with the same software installed. One thing I've changed- turned on customization service to use adaptive battery protection mode.

As for me, I'm thinking about 6.0 downgrade just to calm down :D
[Samsung Galaxy Z Fold 5] stavrone07:
Seems like my phone tries to know a bit more about my habits - here are location usage in the background. Most of the time phone was idling while driving to work

Spoiler content hidden.
[Samsung Galaxy Z Fold 5] _GRIZZLY_:
Are you have AI function on?
[Samsung Galaxy Z Fold 5] stavrone07:
I'm not sure that it is possible to turn them off. The only function in settings is to to process data on the device. And it's turned on since yesterday
[Samsung Galaxy Z Fold 5] _GRIZZLY_:
Yes, then after my ask I want to check by you computing only on phone. But still same effect?
[Samsung Galaxy Z Fold 5] stavrone07:
I will see if it makes any changes. Anyway - took of the charge 1h 43 min ago, got 1 phone call for 3 minutes - now it's 98%. SoT - 4 minutes :)
[Samsung Galaxy Z Fold 5] sosimple:
I'm using 6.1 battery is excellent. Accubattery shows more than 10 hours sot if i use phone without closings screen continually. I loose about 4% in 8 hours sleep which isn't very good but not very bad eather. Battery health is 96% after six months. I have 7-8 hours sot in 24 hours use in real use. No gaming, web, YouTube, light use mostly. 80-90% use in big screen. I dont use original Laucher, im using total launcher if this has anything to do. And in battery settings im not using the typical profile but the other one which uses less battery, i can't find the English word for this.

I have most apps to full freeze in background in battery setting except which i need (Facebook messager etc)

No really difference than before updating.

So i believe 6.1 is excellent. If you have set everything correctly i would factory reset.
[Samsung Galaxy Z Fold 5] SirVss:
Yes! With my brand new Galaxy A55, OneUI 6.1 out of the box, massive battery drain!
[Samsung Galaxy Z Fold 5] _GRIZZLY_:
A55 are very new on the market so nearest updates certainly fix battery
[Samsung Galaxy Z Fold 5] sosimple:
If 6.1 had that massive battery drain, then how come i have the amazing battery im describing above?

Have all of you set all apps that doesn't need to work in background to freeze in background?. Have you formated and set phone again? Have you installed accubattery to see what is your battery consumption with screen of, what with screen on, what app do the consumption? Without those data you can't be sure. If just one app you have, making your phone not to sleep then you will see the worst battery but it won't be 6.1 the reason but an app. Probably tha same app doesn't create problem before, so you think its 6.1 the reason.

Except if its original Laucher which creates the problem. It's the only thing im not using.
[Samsung Galaxy Z Fold 5] SirVss:
Maybe, if they are aware of that, it should, it's well known and reported at this point!
[Samsung Galaxy Z Fold 5] letschky:
The same applies to me with 6.1.

I removed/deactivated unnecessary apps via ADB and got 7-8 hours of SOT,.

Maybe it's slightly worse than with 6.0 but I'm still satisfied.

I didn't do a factory reset from 6.0 to 6.1.

Mine is the F946B.