yashsingh1/xdaforums huggingface dataset:
[Xiaomi Poco F1 Questions & Answers] Taruntj:
Need help, I'm facing this issue, How to fix this?

And my poco F1 was neither connecting to PC nor showing any OTG pendrive. Tried to put the driver all the way for the PC but Poco f1 was not doing anything except charging. Earlier, Pixel experience was installed which was showing updates but showing errors at the time of installation. But this error is coming on installing this ROM

Don't know why OTG pendrive is not being detected in the phone form some time, already changed OTG type C connector or pendrive but nothing is happening. Just by connecting a Type C sugar test machine, the app of that device opens after connect device but OTG pendrive is not showing.

How to fix this issue
[Xiaomi Poco F1 Questions & Answers] roirraW "edor" ehT:
<Moderator Note>:

Hi @Taruntj,

I've merged your other thread about the same issue with this, your slightly earlier thread.

Please familiarize yourself with 📚 XDA Developers Forum Rules 📚, and especially Rule 5:

5. Create a thread topic or post a message only once, this includes external links & streaming media.

As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.

You can bump your unanswered question once every 24 hours

Duplicate threads and posts will be removed

Always post in an existing thread if a topic already exists, before creating a new thread.

Use our search function to find the best forum for your device.

Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.

Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.

Thank you,

@roirraW "edor" ehT
[Samsung Galaxy A02s] janek1311:
Hello,

I've tried to run root and magisk on SM-A025G, but for some reason it failed, anyway i wanted to install ap named worldline tap on mobile, it needs to verify the phone beacuse it takes payments via nfc, and now i installed newest stock rom but the app fails "overall security and integrity" i've disabled bootloader and oem unlock, any ideas how to restart it to "shop" version ?
[Samsung Galaxy A02s] krynyx:
Flashing the stock ROM and wiping all data will restore your device to "shop version".
[Samsung Galaxy A02s] Ragekill3377:
Flash all files which have the same binary number as shown in the download mode (BL AP CP CSC HOME_CSC/USERDATA) via Odin. This will restarte your device to factory settings, remove root and make its firmware like new.

Can you tell what went wrong with magisk? And what steps you took to attempt to root the device?
[Samsung Galaxy A02s] Sal777can:
Starting to doubt samfw or magisk, something added bloat. Check if you have appcloud? it's malicious and wasn't there before, sim toolkit is also duplicated and android system, sketchy.

No kies available, and no way to extract original rom. Trying another csc now.
[OnePlus 8T Questions & Answers] DarkHook:
Hello everyone!

I've been using my 8T KB2003 (EU) for a little over 2 and a half years. About three weeks ago, I began noticing periodic disruptions in cellular network connectivity while using mobile data (4G).

The network loss would persist for a few seconds, during which the device displayed "No SIM," followed by "No service" within a couple of seconds. Shortly after, the cellular network would return. Initially, I dismissed it as a one-time occurrence, but the issue persisted, happening multiple times throughout the day.

To investigate further, I examined the logcat around the time when this behavior occurred. It became apparent that the problem coincided with the crashing of the "oemnvbkdaemon" process, because of a null pointer dereference. The backtrace of the crash is as follows:

I've attempted to search online and understand the precise function of oemnvbkdaemon, but it appears to be a proprietary program from Qualcomm, with limited available information online. Despite efforts, I found only minimal details, except that it is related to the Mobile Data Modem. Examining the backtrace line "/vendor/lib64/liboemnvbk_img_helper.so (oemnvbk_sync_partition_v2.cfi+328)" leads me to assume that oemnvbkdaemon may be attempting to call a function in "liboemnvbk_img_helper.so" responsible for syncing a partition. Unfortunately, the specific partition undergoing this operation remains unclear.

Due to the locked bootloader, I utilized the readback functionality of the MSM Download Tool to back up all partitions, including those with the "oemnvbk" combination in their names:

mdm_oem_dycnvbk

mdm_oem_stanvbk

mdm1oemnvbktmp

Subsequently, I used the MSM Download Tool unbrick method to wipe and restore the device. Interestingly, this process also rewrote the mdm_oem_dycnvbk and mdm_oem_stanvbk partitions. Initially, the device operated without issues for a few days, raising hopes of resolution. Unfortunately, the problem resurfaced today, with the mobile network loss coinciding with another oemnvbkdaemon process crash (the backtrace of the crash above is from today's crash).

Considering the recurrence of this issue, I am beginning to suspect a potential hardware problem. Uncertain about the next steps, I am reaching out here to seek guidance from the community. If anyone has encountered a similar problem or has insights on how to address it, I would greatly appreciate your input.

P.S: I have tried using a different SIM-card, but the problem persisted.
[OnePlus 8T Questions & Answers] Rootk1t:
It seems you're running OOS11.

For the test purposes you can update to the latest OOS13 or 14 with the latest modem firmware and check if this behaviour goes away or persists.

It is persists a hardware seems to be, if not a software one.
[OnePlus 8T Questions & Answers] DarkHook:
I'll do that, and report back the results!
[OnePlus 8T Questions & Answers] DarkHook:
Reporting back after using the latest available version of OOS for my device, OOS13.1 for two weeks, unfortunately, the problem persists in the same manner as it did on OOS11.
[OnePlus 8T Questions & Answers] Rootk1t:
If you've made a clean install of OOS13.1 and problem still persists, i can recommend only trying a custom ROM to finally prove that it is a presumably a hardware issue.
[OnePlus 8T Questions & Answers] DarkHook:
Yes, the process was almost a clean install, I wiped everything and installed OOS11 using the MSMTool and then updated to OOS13.1. I could have wiped and flashed the OOS13.1 zip but I don't think it would have made much of a difference. I will definitely try a custom ROM at some later time to draw a conclusion. Even though I still have my suspicions that it has something to do with the proprietary program from Qualcomm and its attempt to sync a modem partition(which could be corrupted?). But, I unfortunately couldn't find any documentation or information regarding it online.

Thank you for your input!
[OnePlus 8T Questions & Answers] Rootk1t:
Unfortunately i also didn't find any information about oemnvbkdaemon except that

the following files relate to ->

# Qualcomm MDM Interface

vendor/bin/ks

vendor/bin/mdm_helper

vendor/bin/mdm_helper_proxy

vendor/bin/oemnvbkdaemon

vendor/bin/init.mdm.sh

vendor/lib/liboemnvbk_img_helper.so

vendor/lib64/liboemnvbk_img_helper.so

vendor/lib64/libmdmimgload.so

But why does oemnvbkdaemon crash in your case is unknown.

Maybe @BillGoss can help us with the answers?
[OnePlus 8T Questions & Answers] DarkHook:
It is truly a mystery, and all I could guess from the stacktrace is that the process is crashing in a function called "oemnvbk_sync_partition_v2", which is exported by "liboemnvbk_img_helper.so". Furthermore, I am really unsure whether the loss of the cellular network is caused by the crash, or the other way around, that is, the crash is caused by an attempt to synchronize a corrupted partition which is also causing the network loss.

I once again thank you for your efforts!
[OnePlus 8T Questions & Answers] BillGoss:
I can tell you the following:

- mdm_oem_dycnvbk: is not touched by updates and doesn't change over time. The md5sum of mine is 6c5ce63b204d102bb47035dfeb4fecfe and is unchanged since I first got the phone despite all the updates and testing of other ROMs I've done.

- mdm_oem_stanvbk: is included in full OOS update packages so you can re-flash it if necessary and verify its md5sum.

- mdm1oemnvbktmp: isn't touched by updates and changes over time (the *tmp name indicates it's temporary).

- Anything in /vendor is flashed during an update (it's a logical partition in the super partition).

The fact that things work after a clean install but then get worse with time would, in my mind, suggest a software issue. I would expect a hardware issue to affect things randomly - all areas of the RAM chip rather than just one specific location in the chip - but I'm just guessing at this point as I'm not a hardware expert.

Also, the area that's giving you problems (OEM modem) isn't touched by custom ROMs and, therefore, changing ROMs won't/shouldn't have any impact on the problems you're having. But given there's no obvious area that's causing the problem, it won't hurt to try a different rom.
[OnePlus 8T Questions & Answers] DarkHook:
Sorry for the late reply,

I have now checked the md5sum of the mdm_oem_dycnvbk partition, and it is very true that it is unchanged when I compare the one I backed up on OOS11 and the one after I upgraded to OOS13.1, and they both have the md5sum: 14E6AF87A8C3771699B2A4F2FFFE8896

The mdm_oem_stanvbk and mdm1oemnvbktmp partitions on the other hand have different md5sums between the two versions, which I guess is fine, since full updates re-flash mdm_oem_stanvbk and mdm1oemnvbktmp is a temporary partition and changes over time.

I've also tried a clean install of OOS11 without installing any additional software/apps, and unfortunately the issue still persists.
[OnePlus 8T Questions & Answers] Rootk1t:
I can only suggest to kindly ask @BillGoss to provide working copies of his above mentioned permanent partitions like oem_dycnvbk which have different md5 to yours (assuming you both are on the same OOS version).

Maybe some data in that partitions got corrupted on your device, and as MSM Tool doesn't touch them, it persists no matter the ROM you're using.

And in your case the last resort is to flash partitions from another device and see if it changes anything.
[OnePlus 8T Questions & Answers] DarkHook:
I would really be happy to try that, but I don't want to bother @BillGoss too much, as the partition may contain device specific information such as IMEI, and even if not, it may contain different region specific data, as my device is an EU variant KB2003. But if not, I'm open to try stuff, like flashing partitions.
[OnePlus 8T Questions & Answers] BillGoss:
I went back over your initial problem description.

While I understand where you've ended up, the fact that everything works fine initially after using MSM to restore the phone tells me that it's NOT the data in the partitions unique to each phone.

Because, if the problem was there, it would show up immediately, not after a few days.

I'm reluctant to share my partitions data because I'm not sure what it includes. I've previously tried to find where the IMEIDs are stored and I found ONE of them in the persist (sda2) partition. But there should be two of them so I'm worried that they are hidden in some other partition.

I think you'd be better off trying to find what triggers the failures, especially since they start after a few days of a clean install.

You could also snapshot the partitions of interest immediately after a clean install and then after the first failure and see if restoring the initial data makes the problem go away for another number of days. If it does then the partitions that have changed are likely to be the culprits.
[Google Pixel 7a] klkchaitanya:
I have been facing an issue after flashing AOSP 14 (Lynx) onto Pixel 7a devices. As soon as I insert a sim card into the phone, the phone starts rebooting randomly and the phone will not ever connect to the network. The issue is very frequent with the AT&T and Verizon SIM cards. Little less frequent with the T-Mobile sim card, but still happens.

I am wondering if I am missing something or doing something wrong! Here are the steps I am following:

1) I have set up a virtual machine (Ubuntu)

2) I downloaded the source following the steps listed in: https://source.android.com/docs/setup/download/downloading

3) Built AOSP following the steps listed in: https://source.android.com/docs/setup/build/building

4) After a successful build, I download all the FOLDER 'lynx' from the folder WORKING_DIRECTORY/out/target/product/

5) Connect a Pixel 7a in bootloader mode and unlock oem

6) Flash AOSP using the command 'ANDROID_PRODUCT_OUT="./" fastboot flashall -w' from the downloaded lynx folder

7) Phone starts with AOSP 14

8) Insert a sim card

9) The phone keeps rebooting and doesn't connect to the telephone network (It stops being a phone)

I have tried with all the Android 14 (lynx) releases from Oct 2023 to Jan 2024 and no luck! Any help would be greatly appreciated!
[Google Pixel 7a] htc-8925:
what if you flash someone else's precompiled or flash back to stock? issues go away? try from scratch- delete all files and reinstall drivers - OR - live boot a linux machine vs use virtual machine, too much potential for failure in containers
[Google Pixel 7a] numptyman12:
C:\platform-tools>ANDROID_PRODUCT_OUT=extracted fastboot flashall --skip-reboot

'ANDROID_PRODUCT_OUT' is not recognized as an internal or external command,

operable program or batch file.

I Have Fastboot and Adb, SDKtools

The folder im trying to flash is extracted

my Fastboot is in the folder before that,

variables are on the fastboot folder

tried two computers , no idea what im doing wrong
[Sony Xperia XZ1 Compact Questions & Answers] Dfis:
Hi all

I have a brand new Sony Xperia XZ1 Compact, unrooted locked bootloader with stock firmware, and when running the SafteyNet test, it failed on: cts profile match.

Any idea how to fix it?
[Android Q&A, Help & Troubleshooting] alitarekmorsi1:
My phone galaxy a82, one ui 6 but i cant install it
[Sony Xperia 5 III] Hizerxd:
Hey guys.

Is it possible to install the latest version of Game Enhancer on Xperia 5 III, has anyone tried it?
[Samsung Galaxy S24 Ultra] chieco:
Guys I'm so bummed right know.... all the joy I had because of my pre-order is completely gone.

Samsung removed the option of gesture controles where it's basically 3 seperate gestures (swipe from the bottom left for recents, middle for home and right to go back) COMPLETELY!

We are stuck with googles copy of ios's gestures. What's even worse? WE CAN'T HIDE THE GESTURE HINTS! I guess this is so you can trigger circle to search.

I installed OneHandOperation+ to see if there are any options, but nada. We are stuck with a absolute space wasting bar at the bottom of the screen.

Can we do something about this? Am I the only one who is furios about this decision?
[Samsung Galaxy S24 Ultra] Jaxom84:
Indeed, unfortunate evolution for the hint bar. But OneUI 6.1 is going to be released soon for everyone, so let see if Samsung brings back the option to hide it in a future update.
[Samsung Galaxy S24 Ultra] chieco:
Bro this makes me want to cancel my pre-order. And it sucks just to hope that more people will notice and complain to sammy about this for them to bring it back.
[Samsung Galaxy S24 Ultra] Jaxom84:
Well, I'm not sure from which phone you're upgrading from, but if it's a mainstream Android one, get ready to have this on your phone sooner or later.

My wife has a Pixel 8 Pro, and when I noticed she couldn't get rid of the hint bar, I was quite surprised, but it's the way Google is thinking the OS for now.
[Samsung Galaxy S24 Ultra] Guyinlaca:
Wow, that sucks. The ability to use the 3 bottom gestures was one of my favorite Samsung features. Are you sure it's not under "More options"?
[Samsung Galaxy S24 Ultra] TheMystic:
I have never used the bottom up gestures for anything other than going home, so I don't mind this change.

Let's hope Goodlock will come up with an option to hide it.
[Samsung Galaxy S24 Ultra] chieco:
@Jaxom84

You are right! I used samsung the last decade and didn't know what's going on elsewhere. I mentioned this and some people replied that chinese oems also have been removing these options!

Google and Samsung selling a shortcut to google lens as AI and people eating this up is just sad.

Even at the demo I saw what this is for, selling people stuff more easily so the circle of consumerism can be fulfilled. Don't forget Google is all about selling ads and circle search is just a sortcut to find products faster. Even at the demo She was looking up a bag....

@Guyinlaca it's 100% gone in OneUI 6.1. And the update will remove it on older devices. Currently also no way to bring it back with GoodLock, OneHandOperation+ or NaviStar.
[Samsung Galaxy S24 Ultra] Guyinlaca:
If it's anything like OnePlus, they left the option for older models, but took it away starting with the new models. It could be controlled via SetEdit (downloadable app). If it's still on the S23 Ultra after the 6.1 update, then perhaps it can be enabled somehow. Another workaround might be using a Good Lock module to make the 3 button icons invisible, reduce the size of the NavBar and use a gesture app.
[Samsung Galaxy S24 Ultra] chieco:
@Guyinlaca I already experimented with NavStar and you can make the background area transparent and shrink the size of the bar, but can't make it dissapear completely. Also the animations are messed up.

At the end, if Samsung should really not provide a option via GoodLock I will have to root I guess.
[Samsung Galaxy S24 Ultra] Guyinlaca:
Let us know how it goes.
[Samsung Galaxy S24 Ultra] Bigmille:
Is the 3 buttons (back, home, recent) still there please?

I'm looking to give this to my dad after a while, he likes the 3 buttons on his S9+.
[Samsung Galaxy S24 Ultra] mike26301:
You should still be able to use GoodLock OneHandOperation+ for swiping on the corners to go back. And GoodLock NavStar should allow you to hide the navigation bar.
[Samsung Galaxy S24 Ultra] jaseman:
3 button nav? Nova Prime?
[Samsung Galaxy S24 Ultra] Sprov:
Unfortunately, NavStar doesn't let you hide the navigation bar. The option to make it transparent is there but it does nothing as far as I can tell :(
[Samsung Galaxy S24 Ultra] hand-filer:
Still there.
[Samsung Galaxy S24 Ultra] Guyinlaca:
Unfortunately, I confirmed this on a demo S24 Ultra (US model). The gesture hint bar is wide just like an iPhone's too. Google must have put pressure on Samsung. We've got a great development community, so let's hope for a workaround.
[Samsung Galaxy S24 Ultra] Jaxom84:
Actually, if you look closely to your phone (can be easier to notice depending on your wallpaper), the hint bar is located inside a transparent area slightly darker than the rest of your screen. Enabling this option removes that area, leaving the hint bar sitting there without that slight separation.

It took me a few seconds to notice it when I finished transferring my old data to the S24U.
[Samsung Galaxy S24 Ultra] mzayd786:
It's making me want to return my s24 ultra and keep my s23 ultra. I use the 3 swipe gestures and the hiding nav bar and now its completely gone. The bar at the bottom is just a waste of space and annoying 😑
[Samsung Galaxy S24 Ultra] DarkMegans:
I have the S24 Ultra

Got it yesterday and had to realize terribly that Samsung had removed these 3 button gestures

That ruined my enjoyment of the S24 Ultra and I even put the SIM back into the S23U and continue to use the S23U

until there is some hack where you can reinsert this 3 gesture button
[Samsung Galaxy S24 Ultra] MrMike2182:
Do you guys mean this? The navigation bar?View attachment 6059549
[General Questions and Answers] diverdon55:
Hello , I have been using Pdanet for over 10 years ... For the past little while 6 months or so ... It will just drop out by itself .. I have to open it back up and reconnect to use it ... Not a crisis just a little pain ... Samsung s21 plus ... Thank You for any help you can give .. Don
[General Questions and Answers] EllieCat:
I found a thread on Reddit discussing the same issue. Try the methods they use in there.

https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&ved=2ahUKEwi-gLGDjfKDAxUlrYkEHcKRAxcQFnoECB4QAQ&url=https%3A%2F%2Fwww.reddit.com%2Fr%2FHomeNetworking%2Fcomments%2Flzzj8w%2Fanyone_that_uses_pdanet_here_my_internet_keeps%2F&usg=AOvVaw3iyQqGo3axEnh1LxiTux6H&opi=89978449
[General Questions and Answers] diverdon55:
Thank You .. I found a setting in the phone to try ..Thanks to you ..DJ
[General Topics] 69Rixter:
Recently purchased an Ulefone Note 14 running And. 12. My gawd, what an enormous amount of bloatware/spyware/B.S. this O.S. has on it. A phone O.S. that's just over 8Gb??? Ridiculous!!! So, got a few questions #1. Anyone familiar w/ rooting this phone? I'd like to hear from you. Anyone know if this phone will accept/run /e/OS/? Would like to flash that system to this phone if phone is compatible. I'll post the phone's specs----- Ulefone Note 14 Android 12 16Gb internal ROM 3Gb Ram Helio A22 4 core Build # - Note 14_SH1_V02 Would appreciate any help you can offer.

TNX:

Rick
[Pixel C Q&A, Help & Troubleshooting] jlreynolds:
I have a 64GB Pixel C I bought new several years ago.

I've noticed that it's getting very sluggish when the battery drops much below 50% anymore.

I did some research and it looks like a LineageOS ROM installation would be helpful.

Several years ago I had a Motorola Xoom that I rooted and did a ROM upgrade on so I HAD a working knowledge of the process.

I am using a 64-bit Windows 7 HP notebook.

I had some difficulty getting ADB to install and ended up using the 15-Second ADB Installer (as Administrator).

It died on the installation until I added a "Desktop" folder under my user account.

It goes through everything and asks if I want to install the driver and when I tell it Y it completes and says it has installed winusb.

However, when I connect the Pixel C to the computer (Developer Options USB Debugging) the computer doesn't see the Pixel C.

ADB Devices doesn't list it either.

I then tried using the UniveralAdbDriverSetup.msi

It goes through the process and says it was successfully installed but again neither ADB nor the computer see the ixel C.

Finally, I downloaded Android Studio and used SDK Tools.

It says the installation was successful and shows that it is installed in the SDK Tools.

However, as previously neither adb devices nor Windows 7 acknowledge the Pixel as being connected to the computer.

I have used gpedit.msc to tell W& to install unsigned drivers.

Just to clarify I CAN transfer files between the Pixel C and the computer using Windows Explorer so I don't think it's a cable issue.

If I can't even get the Pixel C and the computer to talk to each other via adb I'm not going to be able to do the updated ROM.

It's been a while since I did essentially the same on the Motorola Xoom and I've slept since then but I don't recall having this much trouble getting ready to do the upgrade.

I was a Windows XP computer at that time though.

Any thoughts and direction would be greatly appreciated.

Thanks in advance

Cheers

James
[Pixel C Q&A, Help & Troubleshooting] jlreynolds:
I did a fresh Windows 7 install on an older HP notebook.

I then installed ADB using the 15 Second ADB Installer.

It went through the installation process including the driver installation.

When I connect the Pixel C to it with USB debugging OFF it shows an MTP deice in "Devices & Printers"

The ADB Devices command seems to complete but doesn't list the Pixel C.

If I turn USB debugging ON then the yellow fault triangle shows up beside the MTP device.

Any attempt to follow through with the installation of a driver via "Devices & Printers" fails.

I'd really appreciate some direction.

Thanks in advance.

Cheers

James