yashsingh1/xdaforums huggingface dataset:
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
I flashed vendor_boot.img in boot partition is that the reason for corruption? I don't know what happened with the partitions. Edl itself got broke and I tried many cables and swapped mobo to another good working similar device which my frnd has but still usb unknown error
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] mvikrant97:
You also tried switching motherboard and it still does not work?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
Long pressing power button forces device to boot again and shows mi logo for a second and boots to fastboot directly. In alioth there is edl testpoints. I shorted the testpoints multiple times and tried to connect to PC. And it shows unknown usb device descriptor error and in history of events in usb details I can see the device is already connected and shows the serial numbers too. But for some reason now it's not detecting as 9008 or anything just unknown usb detected
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
Yess
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
I have a hydra edl cable which is not necessary for alioth. But still it's doesn't matter it's not detecting with edl testpoints shorting
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Renate:
Well "unknown device" is a world of difference from "device descriptor failed".

Did you try to load a Windows driver in Device Manager for "unknown device"?

Use Zadig and install WinUsb on that.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
Sorry mam. To be precise that error is unknown usb detected ( device descriptor request failed ). So it detects some device is connected and not communicating with pc . In this pic be5eb582 isa serial number of my device.

View attachment 6060234
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Lagartixo:
I would try a live CD from a Linux distro (see if android-tools is installed by default). Open terminal and type fastboot devices
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
Oh a new method to try. Does this work bro? Cuz guys told that it corrupted abl partition which is responsible for usb detection.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Renate:
Mmm, didn't really say that...

It's looking like the USB board, the flex, the motherboard or the USB PHY interface is dead.

I'd just stay with your Windows until you can get it to read the Device Descriptor.

Do you have a DVM?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Lagartixo:
I had devices (smartphones and TV) that Windows did not detect in any way. I went to Linux and easily recognized. But remember that android-tools has to be installed.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
DVM? I don't know what it is and looked in internet and I don't think I have in my pc. And I'm 101% sure that my cable and usb port in PC as well as in phone all works perfect. I knew it because I do use the cable and the usb port in my pc for other devices to flash nd do stuffs. And in device I have a similar device I swapped the motherboard and using it right now and usb port also working great. Definitely the problem is from the motherboard not hardware it's software as of my knowledge. If u have more points if I'm wrong pls let me know mam. Thanks.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Renate:
A voltmeter.

It's possible that software is the problem with fastboot.

It's not possible that software is the problem with EDL, that is, if you actually got it into EDL mode.

I'm sure that it wouldn't take me long to figure out if the device were here.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
Ok mam now device is in service centre once I get it back I'll let u know and pls tell me the proper way to boot into edl mode. I tried edl test point method to boot into edl mode. Device - mi11x
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
Also I have a multimeter. If it's required yes I have one
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Renate:
Were you shorting the test points while resetting with the power button?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] diyaz97:
most of the time the issue is drivers
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Renate:
True, but when the Windows system can't get the Device Descriptor that's not the case.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] user0u:
In device manager, right click on the usb device and click "uninstall device". Then uninstall and re-install the usb drivers and see if that does anything.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
No mam I just shorted the points and plugged the cable and PC recognised unknown device not the Qualcomm 9008.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
Already tried even much than this sir. But no luck hitting me🥲
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Renate:
Shorting the points while plugging in the cable is correct if the device was fully shutdown.

It's just really hard to do without losing contact on the test points.

When it says "Unknown" does it also say "Device descriptor failed"?

Go to Device Manager, find the device, double-click.

What does "Events" say?

What does "Details", "Property"="Device instance path" say?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
Yes mam it says unknown usb detected with device descriptor request failed. I'll attach the screenshot here for further information.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Renate:
You're looking at old events, but probably the USB is just thrashing.

Odds are it's the USB connector on the phone that is wonky.

I don't think that your playing with voltage/clocks was persistent but maybe the PLL for USB got screwed up?

That would really be unexpected.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
I don't understand what you are trying to say mam. But also yes its the older screenshots so events are old but freshly taken that time with device connected. For now I don't have a device in hand it is in service centre where those technicians failed to boot device and I will collect the device within a day or 2.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] alejandro.pastrana:
It seems you have a computer with AMD processor. I have heard that there are people with connection issues with this CPUs.

If possible, try to connect to a computer with Intel processor. Give it a try

Best regards and good luck
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] user0u:
The screenshot you posted, I see "Ports (COM and LPT)". See what's in that list.

Is it possible the phone is being correctly detected as QDLoader 9008 while you're looking for it under USB controllers?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
Yes bro I know about that AMD incompatible issue I tried with Intel based laptop too same results
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] febry_valdy:
i belive that you need to reball the cpu and ram, good luck.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
One of the user also had the same issue and never rectified even he did cpu reballing still no improvement.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
Hello mam got my device back from service centre. Looks like the scratched the edl point even worse. Now I'll try anything that could revive the device mam. Wait for ur valuable response.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Renate:
So you got it back? Is it working or not working? What did they say? What did they charge you? What did they say that they did?

Since the screen works (still?) it's not a systemic failure.

As I said, the easiest thing to do (for me) would be to start checking the USB connection electrically.

Borrow a digital voltmeter (because you need "diode test") and a USB C to USB A cable (one where the connector is not blue, that is, USB 2.0) that you can cut up.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
So you got it back?

-Yes

Is it working or not working?

-Still the same turns on and fastboot directly

What did they say?

-They can't repair the device.

What did they charge you?

-They charged nothing just they give up on it.

What did they say that they did?

-They tried to flash the rom via fastboot or edl but they miserably failed like me. They didn't opened the protection layer itself everything were intact just edl points are worsen as I mentioned above.

Since the screen works (still?) it's not a systemic failure.

-yes it works as it was before. Seems like nothing was really changed

I have a multimeter mam also I got USB type c pin out board too if incase I need it. Also I have USB cables cutted down too. What should I have to do I'll try it.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Renate:
With a C to C cable plugged into your little board:

Part 1 - put the black lead on "G" (ground), put the DVM in 20 VDC range.

With red lead measure A6, A7, B6, B7, do you see any steady voltage over 0.1V?

Part 2 - put the black lead on "G" (ground), put the DVM in "diode test" (see photo)

With red lead measure A6, A7, B6, B7, do you see any numbers?

Part 3 - put the red lead on "G" (ground), put the DVM in "diode test" (see photo)

With black lead measure A6, A7, B6, B7, do you see any numbers?

That's 12 measurements, enough for a start.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] AVinaSh_S:
I am stuck with same issue :cry:

have you tried https://xdaforums.com/t/fix-unknown...r-request-failed-fastboot-windows-10.3375320/

the key is device specific so instead of 0BB40FF00100 from post, we need to create Mi 11x key.

if anyone can share details of VID PID then may be it might work for us.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
I have another mi11x in hand I'll send u the codes what u u need guide me brother
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
Mod Edit:

Quote removed since post removed.

Looks like somebody hacked into ur account bro
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] AVinaSh_S:
in case you have access to working mi 11x, we can connect in fastboot mode and check VID and PID.

steps,

1. start mi11x in fastboot mode.

2. connect to pc and open device manager

3. check if device listed under "Android Bootloader Interface"

4. right click on it and select "Properties"

5. select "details" tab and "hardware ids" property.

6. share the result and we can try fix from this to skip decription check.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
this is what i got bro
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Renate:
Oh, the last I heard you were getting "device descriptor failed". What changed?

It was rare in the past that you needed to defeat BOS descriptor requests.

Nowadays I would be surprised if a device didn't support it gracefully.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] AVinaSh_S:
Thanks.. tried with no luck.

Tried to connect to old Windows 7 with USB 2.0 port but still nothing.

Guess it is dead for good at this point.

If you get any solution please update the thread.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] AVinaSh_S:
As a final option, I am going to try this (which is also suggested by one helpful user on telegram),

Redmi 9A unbrick Unknown USB Device (Device Descriptor Request Failed)

Just open it up unplug the battery for a few seconds and replug it and its done😉

xdaforums.com

I will visit service center tomorrow to get the back panel open to try this. Will update.

You can also give it a try if you have device opened.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
I already opened my device bro. It's not that tough to open. Also waiting for ur reply after service.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] AVinaSh_S:
If it is open could you try unplugging battery, press power for some time and reconnecting after few mins as mentioned in the post,

Redmi 9A unbrick Unknown USB Device (Device Descriptor Request Failed)

Just open it up unplug the battery for a few seconds and replug it and its done😉

xdaforums.com

will go to local shop to get it open (not confident that i could open it without breaking glass) and try doing above and report back.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
I tried bro not working. Tried many times and different possibilities too still no luck.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] AVinaSh_S:
same experience.

got the device opened and disconnect - reconnected battery.

tried edl mode, no luck.

CPU reballing was not useful for one user and don't want to waste more money or time on this device.

Last Xiaomi for me. This is clearly cheap quality material which does not last over 2 year mark.

Thanks for quick responses in the thread.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Renate:
@srisuren5225 Hey, whatever happened to the DVM checks on the USB line?

Why aren't you checking the obvious?

You've got a breakout board.

This should take 5 minutes.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
Hi mam. Sorry I got no interest in the mean time and now I'm back and also that breakout board is very confusing and I don't have type c to type c cable it's hard for me to check things. Now I cut down the type c to type a cable. Attached a photo of it. Now guide me what to check. Thank you
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Renate:
I presume that you are showing both ends of a cable that you cut all the way through?

People normally just "nibble" at the cable, cut the outside jacket and leave the conductors intact.

Ok, I presume that the top two wires are the "black"?

You need to connect like colors to like again.

Insulate the red connection well, insulate the white connection well.

Put a push button between green (D+) and black (ground).
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
That one was a vooc charging cable which has double wires for high power transfer. Except that it is data + and - with power+&-
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
Done as u said mam. Whats next??....
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Renate:
The photo looks ok.

Turn the device off.

Plug the cable into desktop.

Push and hold the button.

Plug the cable into device.

Wait a few seconds and release the button.

Check for 9008.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
Still the old issue. Not detecting anything else and just by connecting to power device boots to fastboot and upon restarting still boots to fastboot and detecting in pc as unknown device descriptor failed.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Renate:
It still could be your USB board has a bad USB connection.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
No way mam I owe the another same model device and I swapped mobo from it coz of original display in my device and both the usb cable and connection is perfectly working no issues with that. Cable is good, flex cable is good, flex connector is good, port in pc is also good everything is working with other devices and swapped mobo but not with the affected mobo.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Renate:
Well, you're getting me all confused.

Are you saying that the bad MB never shows any USB connectivity (always device descriptor not read) under any mode?

When you say "stuck in fastboot" do you mean that the screen is showing that it is in fastboot (but the USB is dead).
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
Mam device boots to fastboot. Not booting to any even edl boot isn't working. And also usb connectivity always shows only unknown device descriptor. Apart from this no hardware complaint is in device everything from connector to pc port everything is functional. And yes screen is showing fastboot on screen except that it's shows nothing. If I connect to usb or any power source just boots to fastboot. And from pc side it's always a usb unknown error. The push button method u said is also results in same. When I connect usb the device just boots to fastboot and pressing those buttons didn't do anything.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Renate:
I asked you about a zillion posts ago to check connectivity on the USB 2 data lines.

Since you have a ripped up cable you can do that now.

Power off device, plug the cable into device, leave desktop end disconnected.

Use diode test on DVM, black of DVM to black of USB.

Then red of DVM to white of USB, measure.

Then red of DVM to green of USB, measure.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
Done. No change in reading. Shows open connection.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Renate:
That was two readings.

Check with the red & black of the DVM reversed.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
Both the readings were same. And reversed diode test to red and black shows 699.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Renate:
On both?

Well, then it's nominally electrically ok.

It could still be hardware or the abl is corrupt and not initializing USB correctly.

Find the EDL test points, get it in EDL and see if USB is active.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
When I short the edl points and connect to usb device isn't booting to fastboot it's not booting to any and pc is also showing nothing like connected to it.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
I remember I flashed the vendor boot image file in boot partition which may corrupted the abl file. Is there any way to correct it in this condition???
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] srisuren5225:
Mam. I can feel the warmness but device is blank which seems like it is booting to edl mode but usb isn't working. Something regarding usb chip is got problem in mobo not the cpu problem
[Samsung Galaxy S24 Ultra] gregpot2000:
This is my major gripe at the moment, Samsung have completely ruined one of the most useful features.

Previously, it had bright, large, specific colour app icons. It meant I could leave my phone on a table, and see from across the room if I had something important. Eg WhatsApp, or other messaging app.

Now, all the icons are tiny, and the same white colour. What's more, the brightness option has gone so it's constantly too dim! Means this function is useless to me now, as I can't what the icons are without picking phone up!

Anyone else struggling with this? How can I get my old AOD back from S21/23 Ultra?
[Samsung Galaxy S24 Ultra] p.dixon0:
I'm hoping it's just the initial firmware being bugged.

As a bit of a work around, the AOD clock duplicates the Lock Screen clock so you can adjust that clock to try to get the AOD clock that you need, or something similar.

Hopefully they'll address this in an update very soon - the Goodlock module doesn't change anything with the AOD either so has to be something in the firmware.
[Samsung Galaxy S24 Ultra] rosedog:
I too am not liking this new AOD. I would love for it to go back to what I had on my S22U. Small picture/Date+Time/Apps that alternated locations. Not a dimmed version of my lock screen.
[Samsung Galaxy S24 Ultra] SgtChrischi:
I generally like the new AoD. The big problem I have with it is that you can no longer control the brightness and it's just way too dark.
[Samsung Galaxy S24 Ultra] jaseman:
I don't use AOD but I do like the "old" notification LED's that have long ago been removed (stupid idiots) and replaced with Edge Lighting which is NOT configurable! It hasn't worked since inception! Oh sure they added a "short", "medium, and "long" setting but even on long it only stays lit for 5 seconds. WTH?????????

Why go to all the trouble of creating a notification light that cannot be adjusted to stay on until I dismiss it...or give me something to adjust! IT IS USELESS!

So I am forced to use - https://play.google.com/store/search?q=aodnotify&c=apps

It is relatively easy to setup and it works! There's a different version for different OEM's. However, even this version doesn't let you circle the whole screen like the OnePlus version does. can't win!
[Samsung Galaxy S24 Ultra] percussionking:
Upgrading from S21. My wife had a small picture under the clock. Now that option is gone. The only graphical option is to show the lock screen behind the clock. That's super confusing when trying to unlock the phone at night and it's not clear whether you're on the AOD or lock screen.
[Samsung Galaxy S24 Ultra] klisza1993:
Dont care cuz dont use aod at all. But the idea from an iphone is tottaly a mistake.
[Samsung Galaxy S24 Ultra] zoman7663:
The wallpaper being visible on AOD can be turned off in Lockscreen/AOD settings.
[Samsung Galaxy S24 Ultra] omek07:
Is it just me or the AOD and the lockscreen does not work as they were working in the 6.0 ? I am disabling the background and when I restart my phone is enabled again
[Samsung Galaxy S24 Ultra] dinesh6908:
yes same here plus if you keep on AOD, it will suck 15 to 20% battery ever if device is not in use on S24 Ultra.
[Samsung Galaxy S24 Ultra] tvBilly:
The AOD function is not working properly. None of the GoodLock settings for the AOD screen do anything. For a while I suspected aodNotify but that's actually working exactly as it should.

This is the only way to set the AOD screen clock. And as far as I've been able to figure out, the LockScreen available clocks don't support editing or creating your own, just the Samsung supplied ones. I would happily give up seeing a clock in the lock screen to get rid of the clock in the AOD screen. I used to do that by creating a clock with no visible parts...

Every time you "mess" with the AOD/ScreenLock settings in GoodLock the "Show Lock screen wallpaper" setting is turned on in the standard "Settings/LockScreen and AOD/Always On Display". Once you've messed with GoodLock just go back to the standard Settings and reset it.
[Samsung Galaxy S24 Ultra] omek07:
Most of the problems are solved with the new Lockstar . You can even put more that one widget in the lockscreen
[Samsung Galaxy S24 Ultra] tvBilly:
Edit: So I have managed to get my AOD screen devoid of a clock. It involved trying stuff in Clockface. So there is a way. There currently is no clock on my lock screen either now though. I haven't figured out all the different interactions between ClockFace and Lockstar. And what effect turning off the lockscreen and/or AOD sections of Lockstar. Some some of what I said below isn't actually correct... (sorry)

I played a bit with Lockstar (I have the current version) and it's fine for the Lockscreen, but what I create in the AOD section of Lockstar doesn't have any effect on the actual AOD screen.

Whatever clock I choose for the AOD screen is ignored and the clock from the Lockscreen portion is used. Problem is I really don't want a clock on my AOD screen at all and I haven't figured a way to get that. On my S23Ultra (UI6.0 not 6.1) the AOD screen portion of Lockstar worked and I could make an invisible clock (all transparent parts) in the AOD portion of Lockstar. I can't make an invisible clock on the Lockscreen portion though (not sure why it won't let me create my own clock in the Lockscreen part the way it does in the AOD part) Unfortunately (bug?) what I create in the AOD portion is never actually used in the AOD screen.

(I create the clocks and layouts in the ClockFace app in GoodLock. But I think I may be missing something here in the way I'm trying to make this work so I'm gonna play some more with it.)
[Samsung Galaxy S24 Ultra] Liquid Li0n:
the thing that worries me the most, is that it is fixed on the same exact place.

Coming from an S20 Ultra gave me a better feeling that it were not always the same LEDs that had to work.

But even on my S7 Edge was the best. The edge light with the clock and notifications on the side of the phone.
[General Questions and Answers] willdeng:
Hey there, I'm interested in getting a Red Magic 9 Pro, but have had no experience with nubia phones. I've had issues in the past with Chinese phones not being able to properly run Google services like google location history (which I love for the timeline feature) and google opinion rewards. Has anyone tried these services on their 9 Pro (or earlier)?
[Samsung Galaxy Watch 5] olorm73:
I can't pair Galaxy Watch 5 on Vivo x100 pro mobile phone. Can I know how to install 'This watch is not supported by your phone'?