yashsingh1/xdaforums huggingface dataset:
[OnePlus 9] IamTheBRAVE:
Maybe try this?

https://xdaforums.com/t/live-iso-ma...ndroid-devices-without-driver-hassle.3526755/

It's a Usb bootable LiveISO linux distro with all android drivers supported. Might help get your phone detected. Haven't used it so don't know if it'll work for you.

Is your phone booting? Why do you need a connection to PC?
[OnePlus 9] tconn:
I'll take a look at that tonight.

To answer your questions, phone boots and everything else seems to operate just fine. Just checked and boot screen says "Orange State Your device has been unlocked and can no longer be trusted", then like 30 seconds later it boots. It no longer has root after the updates and the only way I know to do it is through adb and fastboot commands. But also I backup my photos to my home PC when it gets pretty full. Also, also I occasionally do mobile development at home and test things on my phone.
[OnePlus 9] IamTheBRAVE:
The orange state is when it's bootloader unlocked. So that's normal. To root, you would indeed need an adb connection even when using the patching boot method.

I just remembered something. Go to your pc, look for a file in Users> your username > .android (hidden folder) > adb.key.

Even when you revoke authorisation from the phone, if that file still exists, the pc still sees 2 different keys so it won't allow it. So see if you can delete it.

Are you on win10 or sbove? It sometimes won't let you connect "untrusted" devices. Hope it helps.
[OnePlus 9] tconn:
Ya, I wasn't too worried about the bootloader message, just being thorough. I'll try the android folder at home also, but for what it's worth I don't have anything android-related on my work computer and it doesn't connect either.

Both are Win10
[OnePlus 9] IamTheBRAVE:
In device manager in win10, do you have any yellow triangle next to android drivers? What are the drivers you installed for your phone?
[OnePlus 9] tconn:
Phone doesn't show anywhere in Device Manager, and no yellow triangles. IIRC, drivers were installed by my phone when I plugged it in at home. I actually don't remember the last time I plugged into my pc at work before now.
[OnePlus 9] IamTheBRAVE:
Then look for your brand's android drivers and install them. I think that's the issue. Plugging the phone alone would install generic android drivers not your specific ones.
[OnePlus 9] tconn:
Short version: Nothing worked.

I had already tried searching for "oneplus 9 drivers". The main site doesn't offer anything, so there are a couple search results that really feel like scam sites. But they're the top results, so maybe I'm wrong. I installed the results from the search, and also searched xda and the one result I found.

I downloaded the ISO for mAid. Ran it in a VM. I couldn't really figure out what to do in it to troubleshoot. I was also discouraged because if my computer won't recognize the device, then why would the device show up in a VM?

I found and removed adbkey and adbkey.pub from "Users\<me>\.android\".

I had a brief bit of hope. I doubt the drivers caused it, so I'll probably remove those again. I got the device to appear in Device Manager but with a yellow triangle. It only seemed to happen when switching between "No data transfer" and "File transfer / Android Auto". The device was displayed as "Unknown USB Device (Device Descriptor Request Failed)". I doubt that provides much help though.
[OnePlus 9] MrSteelX:
Have you tried clearing out the dust bunny's in the usb port on phone?
[OnePlus 9] IamTheBRAVE:
Keep the device in file transfer mode and with a yellow triangle. That's better than nothing.

I found this. Try and install it. (Also, doesn't this forum have a sticky thread for drivers? I have the 9pro btw)

Download Official OnePlus USB Drivers - GSM USB Drivers

Looking for official OnePlus USB Drivers? Then you can download Official OnePlus USB Driver for your Android Smartphone and tablet here.

gsmusbdrivers.com
[OnePlus 9] tconn:
Yup. Folded some paper after the previous stuff. A little bit came out, but not so much that I'd think it's the issue. I have a floss stick thing, but it was a bit thicker and was moving the piece inside the slot.
[OnePlus 9] tconn:
I'm new to XDA, but from what I've seen there's only a sticky for OS Builds
[OnePlus 9] IamTheBRAVE:
Took a look on OP9 forum, doesn't look like there is one. We have that on OP9Pro. Here's a link to the drivers, should work for you i think.

10.26 MB file on MEGA

mega.nz

You can use this thread as tutorial for root (you don't need all parts of it)

https://xdaforums.com/t/guide-magisk-unlock-root-keep-root-oos-13-f-72.4252373//unread
[OnePlus 9] Renate:
"Device Descriptor request failed" tells you that the very first step of USB enumeration failed.

So you're talking about flakey cable, bad connection, interference OR the device was not initialized properly.

So try different ports, different computers, something different.

The first step is getting it to the point where it connects solidly (even if it can't/won't find a driver).

Unfortunately you can't tell Windows to use common sense and install a WinUSB driver. That's why we have Zadig: https://zadig.akeo.ie/

Unfortunately (again), adb.exe expects the correct DeviceInterfaceGUID. Ok, you can patch adb.exe or you can use Zadig with a custom .cfg file to specify the DIGUID.

Here is an example .cfg file. You'll have to fill in the VID/PID/MI if you ever get your phone to connect solidly and you can see that info in the DeviceManager.

So, go to Zadig, select Device > Load Preset File, select Options > List all devices, find your device and hit install.

[device]
Description="Standard Google Device"
VID=0x18d1
PID=0x4ee7
MI=0x00
GUID="{f72fe0d4-cbcb-407d-8814-9ed673d0dd6b}"

Good luck.
[OnePlus 9] tconn:
Dang... I think it's the dust bunnies. I have to push the cord in pretty hard, but it'll connect. So either bunnies or I don't know if the port itself gets displaced over time. Used an air compressor to blow out a bit, might try a bit more tomorrow. Thanks for everyone's help!
[OnePlus 9] MrSteelX:
Try using a toothpick. Just try not to bend port too much.
[OnePlus 9] Sheepmister:
how to use this im noob need help maybe this one can fix my problem
[OnePlus 9] Renate:
No idea. You've given no info.

What's the device, the desktop and any error message?
[OnePlus 9] Sheepmister:
HELP!! Device Description failed error 43

help i just want to flash stockrom but the usb cable is not recognized on pc it says description failed is it the usb type c cable fault cause it is from different brand(tecno brand original cable) am i supposed to use different cable like...

xdaforums.com

Check here
[Huawei Nova 3 Questions & Answers] jaimebo:
Hello guys,

By any chance, Do you know if there is any Custom Rom like "Pixel Experience" for Huawei Nova 3 / Par-lx9 ?

Thank you very much in advance.
[Google Pixel 7] alsansan:
Hello, I'm concerned about my P7 battery, it's draining fast (i'm specially annoyed with screen-off consumption). Nothing really serious I think, knowing it's a common issue with Pixels, but now my device is rooted i want to know what are the best apps, tweaks, etc.. to achieve more time between charges.
[Google Pixel 7] ShadowJP88:
With an apps like SD Maid, you can freeze some apps.

It can also cancel their autostart after boot or even control how and when they react to some events.

It's a powerfull apps that can cause a lot of domage so be carefull ;)
[Google Pixel 7] happynexuss:
I use Naptime... it seems to work pretty well
[Google Pixel 7] krabban:
flash spark os, battery life is fenomenal!

I'm getting over 7hour sot
[Google Pixel 7] alsansan:
I am root and naptime dont let me enter the app. There is a message: "Segup Naptime without root" and instructions to execute two commands in adb. I'm supposing these commands are for non-root users, so what shoud i do to enter the app? Thanks
[Google Pixel 7] happynexuss:
It sounds like Naptime isn't detecting your root. Have you used root checker to confirm you're rooted? or maybe there's a non-root version of the app too and you need to make sure you're using the root version.
[Google Pixel 7] dmbardal:
Doesnt really help when the camera is horrible on SparkOS since you cant update the Pixel Camera Services. (Yet?).
[Google Pixel 7] fullmetal509:
Naptime still works? I havent used it since my nexus 6p! Wasnt sure if it had conflicts with android own "Adaptive Preferences" feature
[Google Pixel 7] alsansan:
I have it working right now in my smartphone (i finally passed the root issue). But I dont know yet if it's working correctly or if there are improvements in battery life.
[Google Pixel 7] w9909989:
does it have gapps?
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] djcaptpln880:
Greetings

Thanks for your reading!

I tried flashing some ROMS onto this phone using download mode using ODIN. I was trying to flash TWRP, MAGISK and LineageOS using some files on this forum to no luck. I am new to ODIN and it appears strange to use!

It appears after doing so that it is going into boot loop mode now and won't boot normally at all.

I can still get into download mode using vol down + bixby + power

But it won't let me go into recovery mode using vol up + bixby + power no matter how long I do it

Can someone point me to the correct files to download and procedure to get this phone up and running again?

Can someone provide assistance?
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] djcaptpln880:
Got it working by using an older version of TWRP! Whew... thanks
[Google TV General] maslibo:
Hi, I couldn't find any information about it on internet.

Is it possible to bypass Google TV to work with 1440p?

I'm using Android SDK to emulate Google TV

edit:/ nvm, i used modified android tv

View attachment 5785375
[Google TV General] chris1892006:
I wish my hisense 43a6h would do 4k in the google tv os.
[Google TV General] chris1892006:
Need to root the A partition not B need the boot.img from partition A not B since it boots to partition A not B because I flashed corrupt boot.img to partition B and it still booted without issue. Need to use Binwalk to extract the firmware .pkg and pull the partition A boot.img.

Please help

43A6H_43A53FUA(0012)_M1114.zip

drive.google.com
[Google Pixel 7] Ejjskakejdndnnxnawjjd:
I notice allot of frame drops and overall GPU performance is shockingly bad, what is wrong with this GPU, is it a power saving GPU or something, Mali g710 is ment to be better than G78 but defo not so far, 10 core gaming not good
[Google Pixel 7] Vio281:
user error :)
[Google Pixel 7] EtherealRemnant:
Sounds like you have a defective device or user error to me as there are lots of people gaming with the Pixel 7 series and finding it fine.
[Google Pixel 7 Pro] Sceleratis:
HI all,

While attempting to update my Pixel 7 Pro (while retaining root, via the modified factory zip method where you root init_boot.img, then replace it in the factory zip, then run google's provided flash-all script) I've been encountering this issue when flash-all reached its last step of flashing the actual zip with the images via fastboot:

"fastboot: error: device requires partition vendor_kernel_boot which is not known to this version of fastboot"

This happens on both the new firmware as well as with the firmware I flashed through this method previously. New firmware after this causes a boot loop, while performing a flash of the old firmware results in the same error but at least gets me back into the system in the state it was in before attempting to upgrade.

Any idea why this is happening? I've ensured fastboot & adb are both up to date and attempted from both Windows and a Fedora laptop both to the same error. It's worth noting I installed the old (current) firmware previously through the same method successfully (before this) so not sure why it's decided to not work now....
[Google Pixel 7 Pro] Sceleratis:
Update: tried again via PixelFlasher and did not encounter the error so I guess if anyone else hits this issue and sees this post.... just use PixelFlasher(?????) No idea the why or how but seems to be good now.
[Google Pixel 7 Pro] Tomadock:
Sounds like you were trying to flash in Fastboot mode rather than FastbootD.
[Google Pixel 7 Pro] Sceleratis:
Negative. I also thought that might be the issue and attempted it (the actual command it was running, not the entire script again since that would reboot to bootloader again) in FastbootD as well to the same result.
[Google Pixel 7 Pro] shamllakh:
i tried the latest version of "SDK Platform Tools"; it worked for me
[Google Pixel 7 Pro] cultofluna:
Literally error says everything....

You need latest platform tools that supports vendor _kernel_boot partition

Google added vendor kernel boot partition on P7 series that's been supported only on latest platform tools
[LG G8 Questions & Answers] Bons007:
I crossflashed Verzon lg g820um to open kor g820nUM

How can i flash evolution x on this phone without brick

I need files
[Google Pixel 7 Pro] Sasaiber:
Hello. Tell me please, does everyone heat up the device to 35 degrees for simple tasks? I'm sitting in a telegram, listening to music through bluetooth headphones and 34 degrees Celsius ... It seems that my Magisk mods are not resource-intensive :(

And yes, I have Magisk Delta. Could it be causing the heat?
[Google Pixel 7 Pro] danw_oz:
Well I would not consider 35 deg overheating
[Google Pixel 7 Pro] Sasaiber:
It's winter now, the room is 13 degrees. And in the summer it will probably be the same as with my last pixel 6 pro - 46 degrees. Near Samsung s22 ultra on snapdragon - 25 degrees in total
[Google Pixel 7 Pro] danw_oz:
I get what your saying it is running hotter than you expect, it is not overheating as per your title.
[Google Pixel 7 Pro] HipKat:
I posted in another thread I Was having heating problems until I flashed the Kirasakura kernel. Now my phone stays up t o10 degrees cooler than on stock.

And DAMN you use a lot of Magisk Modules
[Google Pixel 7 Pro] lil_kujo:
I would say probably that Dolby mod.
[Google Pixel 7 Pro] otonieru:
Streaming music indeed cause overheating to this phone with stock kernel. Spotify is okay. YT Music is disaster.
[OnePlus Nord N10 5G Questions & Answers] TAK13:
Not too long ago i installed a custom rom on my phone( Oneplus nord n10 5g ) and i guess i messed something up cus after a while it would go into Qualcomm crash dump mode. So i went to get help some people told me to use MSM, I installed it, put my phone into EDL mode, ECT, but once i went to click begin with my phone correctly in EDL mode i got the following status msg forever on MSM, "hub-image identify by target sw is disabled". so i thought i got the wrong MSM for the wrong model so i went to get the right one from the official site but there wasn't one for my "BE2026" model so im stumped. Please help.
[OnePlus Nord N10 5G Questions & Answers] gissf1:
Have you seen this forum post: https://xdaforums.com/t/opn105g-oos...l-to-restore-your-device-to-oxygenos.4204445/

I just used that on my BE2026 this morning, and had no issues.
[Google Pixel 6a] G5-User7080:
If you want to remove some preinstalled apps you dont need first check your user id with

adb shell cmd package list users

Usually it's 0, if not then replace it with your user id, then you can simply use

adb shell cmd package uninstall --user 0 <package_name>
adb shell cmd package disable-user --user 0 <package_name>

to uninstall / disable the app over adb.

Attached is a powershell script that removes / disables all apps you put in $removeApps or $disableApps respectively.

The current selection is by no means recommended, it is just a collection that won't result in a bootloop, but thats about it. (yes the commented ones included, they are just commented from the last time I used it)

(change file extension to .ps1 if you want to use it, modify it to fit your needs)

You can always reinstall / enable apps by using

adb shell cmd package install-existing --user 0 <package_name>
adb shell cmd package enable --user 0 <package_name>
[Google Pixel 6a] juv3nal:
Hi,

Thank you for your thorough guide.

I'm stuck after this command:

"fastboot flashing unlock"

I get error "waiting for device"

I have installed the USB drivers as per the link you provided, I think, not sure what's happening.

Any suggestion?

Many thanks.

UPDATE: I used a different USB cable and it worked!! 👍
[Google Pixel 6a] MrUrgit:
Make sure you have enabled OEM unlocking and USB debugging in Developer Options

Also, you can try the command "fastboot devices" to make sure your device is visible to your PC/Laptop.
[Google Pixel 6a] G5-User7080:
^this

if "fastboot devices" doesnt show the id for your phone then the drivers arent working properly.

iirc there might be an issue with the drivers being properly detected sometimes, only had this once on an older computer.

The original now outdated 15s installer has instructions in the"Note" section on how to fix device detection.

if "fastboot devices" returns the device id then I can only think of OEM unlocking being disabled.

if it still doesnt work, consider switching to the full sdk platform tools, idk if it includes the usb drivers.
[Google Pixel 6a] dexlemaffo:
Aswell as using a USB A connected to a USB 2.0 port
[Google Pixel 6a] d_TraXer:
This guide worked very well for unlocking my Pixel 6a.

Sadly I cannot root my device, probably because the newest factory image is from February 2023. Does anyone know where to get the newest factory image from?
[Google Pixel 6a] d_TraXer:
Okay, I managed to bootloop my device lol

How I fixed it + root:

I used the PixelFlasher to downgrade to the newest factory image (from February) + Data Wipe (sadly).

Then I went through your guide again and it successfully got rooted. 😁👍🏻
[Google Pixel 6a] G5-User7080:
Newest Factory Image is from April though.

I linked it under "Prerequisites".

You can use Pixelflasher just fine for rooting as well, check the OTA with Pixelflasher section, it's essentially just applying OTA and "re-rooting".

If you already figured out how to use Pixelflasher you might as well use that to flash factory

You can also check the Pixel 6 Guide that's linked in "sources", that one is very comprehensive and includes multiple methods, just be aware that versions and downloads are different for the Pixel 6a, the general process is the same though.
[Google Pixel 6a] d_TraXer:
Okay that's weird, I checked the link multiple times but everytime I looked the newest factory image was from February. Just now I noticed a banner on top of the page. It says that the website got automatically translated to german. So I switched back to English and now the newest factory image is from April. 🤷

Anyways thank you for your response. Now I can update to the newest version. 😊👍
[Google Pixel 6a] mbellot:
Thanks for the pointer to the MOD version, Integrity Check was only passing Basic with the original safetynet, the MOD version also passes Device now.
[Samsung Galaxy S21 FE] xda-eh:
The following is the highest resolution photo that I got each of these two phones to produce with their best camera settings:

Galaxy J5 (2016): 4128x3096

Galaxy S21 FE: 4000x3000

How does a 6 year old low-end budget phone create photos with more pixels than a 2022 almost-flagship phone?
[Samsung Galaxy S21 FE] blackhawk:
N10+ is 4032×3024

I wouldn't sweat it... smaller/more pixels in the same size sensor doesn't necessarily mean better images. Sensor size maybe different.

Either way the difference is negligible.
[Samsung Galaxy S21 FE] xda-eh:
Shouldn't today's phone's produced pictures that are much bigger than that of 6 years ago?
[Samsung Galaxy S21 FE] blackhawk:
Not necessarily. Even blowing it up you can't see that difference unless you count the pixels. Which produces the better image? Bottom line.

More doesn't mean better.

Individual pixel lense quality matters more.

Larger form factor sensors generally also perform better. These sensors are small so it limits the amount of quality pixels you can use.

That sensor size also limits the amount of light they can gather vs a full frame cam sensor. The small phone cam lens also gather far less light than say a 35 or 50mm lense does.
[Samsung Galaxy S21 FE] GameLogic:
No because a higher resolution doesn't equal to a better quality image. Improvements to the lens, the sensor and the hardware that does the actual image processing is way more important.

And the S21 has optical image stabilizing which the J5 doesn't have.
[Samsung Galaxy S21 FE] xda-eh:
Seems like if the S21 FE's camera is better, it's by a drop.
[Samsung Galaxy S21 FE] blackhawk:
Exactly. Resolution is irrelevant at some point... especially if the individual pixels can't grab a good noise nulling and/or image sample.

12mp is considered ideal for this size sensor, even full frame pro cam sensors top out at around 26mb. One of these will rip a smartphone cam to shreds.

I prefer optical over digital IS.
[Samsung Galaxy S21 FE] xda-eh:
From the little that I tried the S21 FE's camera and compared its photos to the J5, the former's quality doesn't seem much better than the latter. Maybe a drop.
[Samsung Galaxy S21 FE] blackhawk:
Still using the N10+ which grabs good images. What's interesting is I've seen it do the smudging that the S23U users are complaining about. It's not cam shake, light level, wind, shutter speed, focus or subject movement caused; it's seemingly random. Very noticeable with cat fur. Seems to be settings related as it doesn't always happen.

Lately using the same firmware I'm not seeing it (changed the settings)... strange. It's quit annoying when it happens and no way to fix it with post editing.
[Samsung Galaxy S21 FE] xda-eh:
It's just strange that an almost-flagship phone (the S21 FE) has a camera that isn't much of an upgrade in terms of picture quality over a low end 2016 J series phone.
[Samsung Galaxy S21 FE] SirRGB:
I doubt it. Especially in low light the software kicks in and makes the j5 look old. OIS obviously helps to get steady shots.
[Samsung Galaxy S21 FE] blackhawk:
The N10+ was a quantum leap from my old S4+ in everything including cams.

In my opinion the N10+ was Samsung's overall zenith in flagship design. Android 9 was Gookill's zenith. Both started screwing up on subsequent models/versions. The lack of expandable storage is both an overreach and reprehensible; it doesn't serve the consumer but rather Google's and Samsung's agendas. Once Samsung stop calling it a Note it was broke...
[Samsung Galaxy S21 FE] xda-eh:
The low-end A12 from December 2020 has a 48 MP camera, while the S21 FE has a 12 MP camera.
[Samsung Galaxy S21 FE] blackhawk:
Both are underwhelming. Guess Samsung thought the 48mp cam would make the A12 more appealing. Oddly it has the expandable storage and 3.5mm jack.

A used N10+ is a more capable phone than both, Samsung's a mess. They've been undermining themselves for years now. Poor leadership.
[Samsung Galaxy S21 FE] xda-eh:
Well, in the case of the low-end A12 it may be excusable, but for the $700 priced S21 FE it’s inexcusable. Along with the S21 FE’s lousy battery that drains much quicker than the advertised amount. Not to mention its touch and scroll glitches.
[Samsung Galaxy S21 FE] blackhawk:
My point exactly. You can buy a new N975U1* for less than $700 even now. Better yet they're factory loaded with Android 10 although I think Pie is better. Poor SOT has gotten to be a major issue since the N10+; Samsung's solution is to put increasing larger capacity Li's and even then the N10+ is getting better SOT.

Great... heavier, thicker phones with megapixel counts like the pro movie cams have (except their performance justify it).

Samsung's morphed into a hyped up hot mess🤣

*new Exynos variants are priced considerably higher (demand) because they can be rooted. Otherwise they are less capable than the Snaps.
[Samsung Galaxy S21 FE] xda-eh:
Yup. Major problem.

Snapdragon phones can't be rooted?
[Samsung Galaxy S21 FE] blackhawk:
Likely not. There were/are some sites charging money to do so remotely. They're using their Knox Developer privileges to so, until Samsung catches up to them. I think that's what's going on... my interest is minimal.

Giving anyone remote access permission is unacceptable and bricking a good N10+ is something I personally wouldn't risk as they run well stock (and securely even on Pie) after being optimized.